Triple
T5723317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaedra |
E126200
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Androgeus |
E141380
|
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: Androgeus | Statement: [Phaedra, sibling, Androgeus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Androgeus Context triple: [Phaedra, sibling, Androgeus]
-
A.
Androgeus
chosen
Androgeus is a figure in Greek mythology, a son of King Minos of Crete whose death in Athens helped spark the conflict that led to the legend of the Minotaur and the Athenian tributes.
-
B.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
-
C.
Pleistarchus
Pleistarchus was a 5th-century BC Eurypontid king of Sparta and son of the famous Spartan leader Pausanias.
-
D.
Amphictyon
Amphictyon is a figure in Greek mythology, traditionally regarded as an early king of Athens and associated with the legendary Amphictyonic League.
-
E.
Amphimachus
Amphimachus is a minor figure in Greek mythology known primarily as one of the sons of Electryon, king of Mycenae and father of Alcmena, the mother of Heracles.
- 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_69c07dfa10a88190b2e95987229915f5 |
completed | March 22, 2026, 11:40 p.m. |
Created at: March 22, 2026, 3:46 p.m.