Triple
T8230339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tantalus |
E192275
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Niobe |
E113750
|
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: Niobe | Statement: [Tantalus, fatherOf, Niobe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niobe Context triple: [Tantalus, fatherOf, Niobe]
-
A.
Niobe
chosen
Niobe is a figure in Greek mythology whose tragic story centers on her pride in her many children and the devastating divine retribution that followed.
-
B.
Antiope
Antiope is an Amazonian queen in Greek mythology, often associated with Athens through her relationship with the hero Theseus.
-
C.
Antiope
Antiope is a figure in Greek mythology, often associated with Thebes and known for her tragic story involving Zeus and the birth of the twins Amphion and Zethus.
-
D.
Creusa
Creusa is a figure in Greek mythology, often depicted as an Athenian princess and mother of Ion in Euripides’ tragedy.
-
E.
Creusa
Creusa is a figure in Greek mythology, best known as a Trojan princess and the wife of the hero Aeneas.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78035b488190bfd6b6c5d7b7c002 |
completed | March 31, 2026, 7:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd94e168688190aa0a7149a4f8c4b0 |
completed | April 1, 2026, 9:57 p.m. |
Created at: March 30, 2026, 5:46 p.m.