Triple
T19337866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labdacus |
E483667
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Polydorus |
—
|
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: Polydorus | Statement: [Labdacus, predecessor, Polydorus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polydorus Context triple: [Labdacus, predecessor, Polydorus]
-
A.
Polydorus
Polydorus is a figure in Greek mythology, traditionally known as a son of Cadmus and Harmonia and thus a Theban prince.
-
B.
Polydorus
chosen
Polydorus is a figure in Greek mythology, traditionally known as the youngest son of King Priam of Troy whose tragic death is recounted in various ancient sources.
-
C.
Polydorus of Pherae
Polydorus of Pherae was a 4th-century BC Thessalian ruler associated with the tyrannical dynasty that controlled the city of Pherae in ancient Greece.
-
D.
Deiphontes
Deiphontes is a figure in Greek mythology known as a Heraclid prince and son-in-law of Temenus, associated with the royal lineage of Argos.
-
E.
Orestheus
Orestheus is a minor figure in Greek mythology known primarily as a son of the flood survivor and progenitor of humankind, Deucalion.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61646e89081908c9f1d2cf557672c |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 10, 2026, 1:33 p.m.