Home › Entities › events_in_a_specific_year_or_time_period › conflicts in 1768

conflicts in 1768

VisualArtwork events_in_a_specific_year_or_time_period Q10548790
Press Enter · cited answer in seconds

conflicts in 1768

Summary

conflicts in 1768 is an events in a specific year or time period[1].

Key Facts

  • conflicts in 1768's instance of is recorded as events in a specific year or time period[2].
  • conflicts in 1768's follows is recorded as conflicts in 1767[3].
  • conflicts in 1768's followed by is recorded as 1769 in military history[4].
  • conflicts in 1768's point in time is recorded as +1768-01-01T00:00:00Z[5].
  • conflicts in 1768's topic's main category is recorded as Category:Conflicts in 1768[6].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [2] ↑ . wikidata.org.
  2. [3] ↑ . wikidata.org.
  3. [4] ↑ . wikidata.org.
  4. [5] ↑ . wikidata.org.
  5. [6] ↑ . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). conflicts in 1768. Retrieved May 3, 2026, from https://4ort.xyz/entity/conflicts-in-1768
MLA “conflicts in 1768.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/conflicts-in-1768.
BibTeX @misc{4ortxyz_conflicts-in-1768_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{conflicts in 1768}}, year = {2026}, url = {https://4ort.xyz/entity/conflicts-in-1768}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): conflicts in 1768 — https://4ort.xyz/entity/conflicts-in-1768 (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/conflicts-in-1768 · Last refreshed: