Triple
T5723321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaedra |
E126200
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Theseus |
E30832
|
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: Theseus | Statement: [Phaedra, spouse, Theseus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Theseus Context triple: [Phaedra, spouse, Theseus]
-
A.
Theseus
chosen
Theseus is a legendary hero of Greek mythology best known for slaying the Minotaur and serving as the mythical king and unifier of Athens.
-
B.
Teseo Tesei
Teseo Tesei was an Italian naval officer, engineer, and pioneer of manned torpedoes during World War II, regarded as a hero of the Italian Royal Navy’s special assault units.
-
C.
Thésée
Thésée is a French Baroque opera (tragédie en musique) by Jean-Baptiste Lully, based on the myth of Theseus and first performed in 1675.
-
D.
Perseus
Perseus is a legendary Greek hero famed for slaying the Gorgon Medusa and rescuing Andromeda.
-
E.
Hippolyte
Hippolyte is a tragic hero from Greek mythology, known as the chaste son of Theseus whose doomed love and fatal misfortunes have inspired numerous literary and operatic works.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024e6c444819089270b188e60cc67 |
completed | March 22, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a80aefc8190b6ea35ab405ea502 |
completed | March 22, 2026, 9:09 p.m. |
Created at: March 22, 2026, 3:46 p.m.