Triple
T6157780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thyone |
E137364
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Cadmus |
E121008
|
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: Cadmus | Statement: [Thyone, father, Cadmus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cadmus Context triple: [Thyone, father, Cadmus]
-
A.
Cadmus
chosen
Cadmus is a legendary Phoenician prince in Greek mythology, famed as the founder and first king of Thebes and the bringer of the alphabet to the Greeks.
-
B.
Erichthonius
Erichthonius is a legendary early king of Dardania in Greek mythology, often regarded as an ancestor of the Trojan royal line.
-
C.
Cranaus
Cranaus is a legendary early king of Athens in Greek mythology, often associated with the city's primeval history before the time of more famous rulers like Erechtheus and Theseus.
-
D.
Cretheus
Cretheus is a figure in Greek mythology, a king of Iolcus and ancestor of the hero Jason.
-
E.
Acrisius
Acrisius is a king in Greek mythology, best known as the father of Danaë and the ill-fated grandfather of the hero Perseus.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3177588190970a45af0d43b04c |
completed | March 22, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1418ba6488190aaf8d3070555d60a |
completed | March 23, 2026, 1:35 p.m. |
Created at: March 22, 2026, 4:17 p.m.