Triple

T19170723
Position Surface form Disambiguated ID Type / Status
Subject Antenor E469311 entity
Predicate children P980 FINISHED
Object Laodocus NE NERFINISHED

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: Laodocus | Statement: [Antenor, children, Laodocus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laodocus
Context triple: [Antenor, children, Laodocus]
  • A. Laodocus chosen
    Laodocus is a minor figure in Greek mythology, known primarily as a son of Timandra.
  • B. Laodamas
    Laodamas is a figure in Greek mythology, known as a Theban leader and son of Eteocles who fought against the Epigoni in the war for Thebes.
  • C. Laodamas
    Laodamas is a prince in Greek mythology, best known as the favored son of King Alcinous of the Phaeacians in Homer's Odyssey.
  • D. Deinomenes
    Deinomenes was an ancient Greek figure known primarily as the father of Gelon, the powerful tyrant of Gela and Syracuse in the early 5th century BCE.
  • E. Antonidas
    Antonidas is a powerful human archmage and former leader of the Kirin Tor in the Warcraft universe, renowned for his wisdom and pivotal role in the events surrounding the fall of Lordaeron.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f163c5888190b4880471d17b4f51 completed April 20, 2026, 9:26 a.m.
Created at: April 10, 2026, 12:06 p.m.