Triple
T19083663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polydorus |
E467089
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Deiphobus |
—
|
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: Deiphobus | Statement: [Polydorus, sibling, Deiphobus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deiphobus Context triple: [Polydorus, sibling, Deiphobus]
-
A.
Deiphobus
chosen
Deiphobus is a prince of Troy in Greek mythology, known as one of Priam's sons and a prominent warrior during the Trojan War.
-
B.
Pleistarchus
Pleistarchus was a 5th-century BC Eurypontid king of Sparta and son of the famous Spartan leader Pausanias.
-
C.
Iphiclus
Iphiclus is a figure in Greek mythology known primarily as a son of Thestius and thus a member of the royal family of Calydon.
-
D.
Leonnatus
Leonnatus was a Macedonian nobleman and general who served under Alexander the Great and later emerged as one of the Diadochi, the rival successors who contested control of Alexander’s empire.
-
E.
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.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34600f88190bd96bcc2c5c08d14 |
completed | April 20, 2026, 8:26 a.m. |
Created at: April 10, 2026, 12:04 p.m.