Triple
T3370327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troezen |
E70938
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | Pittheus |
E354010
|
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: Pittheus | Statement: [Troezen, governedBy, Pittheus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pittheus Context triple: [Troezen, governedBy, Pittheus]
-
A.
Pittheus
chosen
Pittheus is a figure in Greek mythology, known as the wise king of Troezen and grandfather of the hero Theseus.
-
B.
Aristaeus
Aristaeus is a minor Greek god associated with agriculture, beekeeping, and pastoral pursuits, often revered as a culture hero who taught humans various rural arts.
-
C.
Aeacus
Aeacus is a just and pious king from Greek mythology who ruled the island of Aegina and later became one of the three judges of the dead in the underworld.
-
D.
Demophon
Demophon is a figure in Greek mythology, traditionally known as one of the sons of the Athenian hero Theseus and later a king of Athens.
-
E.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bb32f88190bacf50e11b50fe99 |
completed | March 8, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b35460b4a081908f05bf786cc9bcd3 |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:13 p.m.