Triple
T19134224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echephron |
E468393
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Neleus |
—
|
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: Neleus | Statement: [Echephron, relative, Neleus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neleus Context triple: [Echephron, relative, Neleus]
-
A.
Neleus
chosen
Neleus is a figure in Greek mythology, a son of Poseidon who became king of Pylos and fathered the heroic lineage that included Nestor.
-
B.
Hyllus
Hyllus is a figure in Greek mythology known as the son of Heracles and Deianira, often associated with the Dorian invasion and the Heracleidae.
-
C.
Helvius
Helvius is an ancient Roman family name (nomen) associated with members of the Helvia gens, such as the physician Helvius Successus.
-
D.
Nethuns
Nethuns is an Etruscan god primarily associated with water, especially wells and the sea, and is often linked to the later Roman god Neptune.
-
E.
Temenus
Temenus is a mythological Greek hero and king, a descendant of Heracles who played a key role in the Dorian invasion and the founding of Argos’s royal line.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
Created at: April 10, 2026, 12:05 p.m.