Triple
T4943727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurymachus |
E110996
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Polybus |
E110996
|
NE FINISHED |
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: Polybus | Statement: [Eurymachus, father, Polybus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polybus Context triple: [Eurymachus, father, Polybus]
-
A.
Polybus
chosen
Polybus is a minor figure in Greek mythology known primarily as the father of Eurymachus, one of the leading suitors of Penelope in Homer's Odyssey.
-
B.
Polybus
Polybus is the king of Corinth in Greek mythology who raises Oedipus as his own son.
-
C.
Praxeas
Praxeas was an early Christian theologian known for promoting a modalistic view of the Trinity that was later deemed heretical by mainstream church authorities.
-
D.
Bertramus
Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
-
E.
Médard
Médard is a masculine French given name of Christian origin, historically associated with Saint Médard and used in various Francophone regions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77c421288190bcc2d9bfdfff7198 |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:31 p.m.