Triple
T13573049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thessalians |
E324211
|
entity |
| Predicate | mythologicalAncestor |
P9595
|
FINISHED |
| Object | Thessalus |
E818579
|
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: Thessalus | Statement: [Thessalians, mythologicalAncestor, Thessalus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thessalus Context triple: [Thessalians, mythologicalAncestor, Thessalus]
-
A.
Thessalus
chosen
Thessalus is a figure from Greek mythology, traditionally known as a son of the hero Jason and Alcimede.
-
B.
Erasinos
Erasinos is an ancient river in the region of Attica, Greece, historically associated with the sanctuary and coastal area of Brauron.
-
C.
Dagisthaeus
Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
-
D.
Isander
Isander is a minor figure in Greek mythology known primarily as a son of the hero Bellerophon.
-
E.
Sthenelus
Sthenelus is a figure in Greek mythology, known as a king of Mycenae and a descendant 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f8bda0c81909afd4b9ef9605cd3 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:48 p.m.