Triple
T4736719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priam |
E105142
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Polydorus |
E121013
|
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: Polydorus | Statement: [Priam, father, Polydorus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polydorus Context triple: [Priam, father, Polydorus]
-
A.
Polydorus
chosen
Polydorus is a figure in Greek mythology, traditionally known as a son of Cadmus and Harmonia and thus a Theban prince.
-
B.
Orestheus
Orestheus is a minor figure in Greek mythology known primarily as a son of the flood survivor and progenitor of humankind, Deucalion.
-
C.
Aegisthus
Aegisthus is a figure in Greek mythology known for his affair with Clytemnestra and his role in the murder of King Agamemnon, which led to his eventual killing by Orestes.
-
D.
Laius
Laius is a mythological king of Thebes in Greek tragedy, best known for the prophecy that his son would kill him and marry his wife, setting the stage for the story of Oedipus.
-
E.
Deiphobus
Deiphobus is a prince of Troy in Greek mythology, known as one of Priam's sons and a prominent warrior during the Trojan War.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be10b49b90819091c3ab38e976baeb |
completed | March 21, 2026, 3:29 a.m. |
Created at: March 20, 2026, 1:19 p.m.