Triple
T19832631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admete |
E476500
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Eurybius |
—
|
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: Eurybius | Statement: [Admete, sibling, Eurybius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurybius Context triple: [Admete, sibling, Eurybius]
-
A.
Eurybius
chosen
Eurybius is a minor figure in Greek mythology known primarily as one of the sons of Neleus, the king of Pylos.
-
B.
Aristodemus of Nysa
Aristodemus of Nysa was an ancient Greek grammarian and scholar from the city of Nysa, known for his work on language and literary criticism.
-
C.
Deimachus
Deimachus is a relatively obscure figure in Greek mythology known primarily as the son of Enarete.
-
D.
Deimachus
Deimachus is a relatively obscure figure in Greek mythology known primarily as the father of Neleus, the future king of Pylos.
-
E.
Aristodemus
Aristodemus is a figure in Greek mythology, one of the Heracleidae and a descendant of Heracles associated with the legendary return of his lineage to the Peloponnese.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656cf7e488190b4be28b5e7b363bf |
completed | April 20, 2026, 4:39 p.m. |
Created at: April 10, 2026, 1:50 p.m.