Triple
T4296275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariadne |
E99720
|
entity |
| Predicate | father |
P120
|
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: [Ariadne, father, Minos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Minos Context triple: [Ariadne, father, 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.
Hekademos
Hekademos (or Hecademus) was an Athenian hero or local figure whose grove outside Athens became the site of Plato’s Academy, giving the school its name.
-
C.
Acrisius
Acrisius is a king in Greek mythology, best known as the father of Danaë and the ill-fated grandfather of the hero Perseus.
-
D.
Rhadamanthus
Rhadamanthus is a figure from Greek mythology renowned as a wise and just ruler who, after death, became one of the judges of the dead in the underworld.
-
E.
Cretheus
Cretheus is a figure in Greek mythology, a king of Iolcus and ancestor of the hero Jason.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509aebd48190af38f2e37f07869a |
completed | March 12, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5c7439b3481908d2554f7b86002aa |
completed | March 14, 2026, 8:38 p.m. |
Created at: March 12, 2026, 11:08 p.m.