Triple

T38292470
Position Surface form Disambiguated ID Type / Status
Subject Afsharid military campaigns E1022396 entity
Predicate instanceOf P0 FINISHED
Object 18th-century military history event C48589 CONCEPT FINISHED

How this triple was built (1 step)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: 18th-century military history event
Context triple: [Afsharid military campaigns, instanceOf, 18th-century military history event]
  • A. 18th-century military operation chosen
    An 18th-century military operation is a coordinated campaign or action conducted by armed forces of that era, typically involving formal armies, linear tactics, and logistical planning within the political and technological constraints of the time.
  • B. 18th-century event
    An 18th-century event is a historically significant occurrence between 1701 and 1800 that reflects the political, social, cultural, or technological developments of that period.
  • C. early 18th-century conflict
    An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
  • D. 17th-century event
    A 17th-century event is a historically significant occurrence between 1601 and 1700 that influenced the political, social, cultural, or scientific development of its time.
  • E. Revolutionary War event
    A Revolutionary War event is a significant occurrence—such as a battle, political decision, treaty, or social upheaval—that directly influenced the course, conduct, or outcome of the American Revolutionary War.
  • F. None of above.

Provenance (1 batch)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f76df190f081908d5aa02c8a9286d0 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:30 p.m.