Triple
T9702439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeson |
E234809
|
entity |
| Predicate | childOf |
P120
|
FINISHED |
| Object | Cretheus |
E234811
|
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: Cretheus | Statement: [Aeson, childOf, Cretheus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cretheus Context triple: [Aeson, childOf, Cretheus]
-
A.
Cretheus
chosen
Cretheus is a figure in Greek mythology, a king of Iolcus and ancestor of the hero Jason.
-
B.
Pheneus
Pheneus was an ancient Arcadian city in the northeastern Peloponnese, known from Greek mythology and classical geography.
-
C.
Salmoneus
Salmoneus is a figure in Greek mythology, a king of Elis known for his hubristic attempt to imitate Zeus and for being the father of Tyro.
-
D.
Erichthonius
Erichthonius is a legendary early king of Dardania in Greek mythology, often regarded as an ancestor of the Trojan royal line.
-
E.
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.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19132687c8190baf3a60af1b789a8 |
completed | April 4, 2026, 10:31 p.m. |
Created at: March 30, 2026, 8:18 p.m.