Triple
T669642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo |
E12942
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Minos |
E24192
|
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: Minos | Statement: [Apollo, sibling, Minos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Minos Context triple: [Apollo, sibling, Minos]
-
A.
Minos
chosen
Minos is a legendary king of Crete in Greek mythology, famed for commissioning the Labyrinth and serving as a judge of the dead in the underworld.
-
B.
Nausithous
Nausithous is a lesser-known figure in Greek mythology, traditionally named as one of the sons of the nymph Calypso.
-
C.
Cronos
Cronos is a 1993 Mexican horror-fantasy film directed by Guillermo del Toro, noted for its inventive vampire mythology and atmospheric visual style.
-
D.
Cronus
Cronus is a Titan in Greek mythology best known for overthrowing his father Uranus and later being overthrown by his own son Zeus.
-
E.
Linos
Linos is an alternative form of the name Linus, often associated with figures from ancient Greek mythology and early Christian tradition.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ffbe09881909b547a52a6b34c7f |
completed | March 1, 2026, 8:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a64a4f8f0081909686a76b4fddda60 |
completed | March 3, 2026, 2:41 a.m. |
Created at: March 1, 2026, 7:36 p.m.