Triple
T11840028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autolychus |
E281623
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Anticlea |
E111367
|
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: Anticlea | Statement: [Autolychus, child, Anticlea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anticlea Context triple: [Autolychus, child, Anticlea]
-
A.
Anticlea
chosen
Anticlea is a figure in Greek mythology best known as the mother of the hero Odysseus and the wife of Laertes.
-
B.
Creusa
Creusa is a figure in Greek mythology, often depicted as an Athenian princess and mother of Ion in Euripides’ tragedy.
-
C.
Creusa
Creusa is a figure in Greek mythology, best known as a Trojan princess and the wife of the hero Aeneas.
-
D.
Kleia
Kleia is a Kyrian soulbind NPC in World of Warcraft: Shadowlands, known for forming powerful bonds with players in the Bastion covenant.
-
E.
Lycomède
Lycomède is a character from Greek mythology, traditionally depicted as a king associated with the stories surrounding Achilles and other heroic figures.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a63106b48190917817ec40d21a49 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1678668ac81909bddf67e8c176757 |
completed | April 29, 2026, 2:05 a.m. |
Created at: April 8, 2026, 9:43 p.m.