Triple
T19970284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oechalia |
E480051
|
entity |
| Predicate | hasKing |
P25268
|
FINISHED |
| Object | Eurytus |
—
|
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: Eurytus | Statement: [Oechalia, hasKing, Eurytus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurytus Context triple: [Oechalia, hasKing, Eurytus]
-
A.
Eurytus
chosen
Eurytus is a famed archer-king in Greek mythology, known as the ruler of Oechalia and a rival of Heracles in archery and in love.
-
B.
Telophorus
Telophorus is a genus of bushshrikes, medium-sized insectivorous passerine birds native to sub-Saharan Africa.
-
C.
Tementhes
Tementhes is an alternative name for Tantamani, a Kushite pharaoh of Egypt’s 25th Dynasty known for his attempts to restore Nubian rule over Egypt.
-
D.
Neocles
Neocles was an Athenian of the late 6th century BC, best known as the father of the prominent statesman and general Themistocles.
-
E.
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.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc89b508190879d29bef546aac8 |
completed | April 20, 2026, 5 p.m. |
Created at: April 10, 2026, 1:54 p.m.