Triple

T38168204
Position Surface form Disambiguated ID Type / Status
Subject Russian campaign in the Peloponnese E953205 entity
Predicate instanceOf P0 FINISHED
Object 18th-century military intervention 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 intervention
Context triple: [Russian campaign in the Peloponnese, instanceOf, 18th-century military intervention]
  • 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. 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.
  • C. 19th-century conflict
    A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
  • D. seventeenth-century war
    A seventeenth-century war is a large-scale, organized armed conflict between states or factions during the 1600s, shaped by emerging nation-states, religious and dynastic rivalries, and evolving gunpowder military technology.
  • E. Dutch colonial military campaign
    A Dutch colonial military campaign is an organized series of armed operations conducted by the Netherlands to conquer, pacify, or control territories and populations within its overseas empire.
  • 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_69f76f0b93c48190a117319ab3a9f282 completed May 3, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:21 p.m.