Triple
T21896955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neleid dynasty |
E540703
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Echephron (son of Nestor) |
—
|
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: Echephron (son of Nestor) | Statement: [Neleid dynasty, hasMember, Echephron (son of Nestor)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Echephron (son of Nestor) Context triple: [Neleid dynasty, hasMember, Echephron (son of Nestor)]
-
A.
Aretus (son of Nestor)
Aretus, son of Nestor, is a minor figure in Greek mythology known primarily as one of the many children of the wise Pylian king who fought in the Trojan War.
-
B.
Echephrōn
chosen
Echephrōn is a minor figure in Greek mythology, known primarily as one of the sons of the hero Nestor, king of Pylos.
-
C.
Temenus of Argos
Temenus of Argos is a legendary Heraclid king of Argos in Greek mythology, regarded as an ancestor of the Argead dynasty of Macedon.
-
D.
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.
-
E.
Thrasymedes
Thrasymedes is a figure in Greek mythology, a son of Nestor who fought as a warrior in the Trojan War.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc700c08190a470fe1ad76c8509 |
completed | April 28, 2026, 8:59 p.m. |
Created at: April 16, 2026, 7:07 p.m.