Triple

T12386266
Position Surface form Disambiguated ID Type / Status
Subject Battle of Leuctra E295872 entity
Predicate commander P1061 FINISHED
Object Pelopidas E302144 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Pelopidas | Statement: [Battle of Leuctra, commander, Pelopidas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pelopidas
Context triple: [Battle of Leuctra, commander, Pelopidas]
  • A. Pelopidas chosen
    Pelopidas was a prominent 4th-century BCE Theban statesman and general, known for his leadership of the Sacred Band and his role in challenging Spartan dominance in Greece.
  • B. Perieres of Messenia
    Perieres of Messenia is a figure in Greek mythology, a Messenian king associated with the royal line of Perseus through his marriage to Gorgophone.
  • C. Ligkiades
    Ligkiades is a village in northwestern Greece overlooking Lake Pamvotida, known for its scenic views and tragic World War II history.
  • D. Cleonymus
    Cleonymus is a relatively obscure figure in Greek mythology known primarily as a descendant of the hero Heracles through his father Iphicles.
  • E. Leonidas of Naxos
    Leonidas of Naxos was an ancient Greek figure from the island of Naxos, notable enough in antiquity to have the Leonidaion building named in his honor.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fbd489c819098233a111442762e completed April 10, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6347816408190904ea71d2a72398f completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:54 p.m.