Triple

T35568371
Position Surface form Disambiguated ID Type / Status
Subject Corinthian troops E1027841 entity
Predicate instanceOf P0 FINISHED
Object ancient Greek military forces C31291 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: ancient Greek military forces
Context triple: [Corinthian troops, instanceOf, ancient Greek military forces]
  • A. ancient Greek military force chosen
    An ancient Greek military force is an organized body of citizen-soldiers, often centered around the hoplite phalanx and supported by various specialized units, mobilized by a polis or coalition to conduct warfare and defend its political interests.
  • B. hoplite army
    A hoplite army is a heavily armed infantry force of citizen-soldiers fighting in close formation, typically organized into phalanxes using spears, shields, and armor for collective defense and offense.
  • C. ancient Greek war
    Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
  • D. ancient Greek alliance
    An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
  • E. ancient mercenary group
    A diverse band of professional soldiers-for-hire from antiquity, bound by contract rather than loyalty, who sell their martial skills to the highest bidder in foreign wars and political conflicts.
  • 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_69f76e020fd8819081cb080e7e203083 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:04 p.m.