Triple
T10627736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autolycus |
E250365
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Aesimus |
E250365
|
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: Aesimus | Statement: [Autolycus, child, Aesimus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aesimus Context triple: [Autolycus, child, Aesimus]
-
A.
Aesimus
chosen
Aesimus is a minor figure in Greek mythology known primarily as the son of the trickster Autolycus.
-
B.
Aethlius
Aethlius is a figure in Greek mythology, often regarded as an early king of Elis and associated with the lineage of heroic rulers.
-
C.
Archemorus
Archemorus is a figure in Greek mythology, originally named Opheltes, whose death as an infant—while under the care of Hypsipyle—was seen as an ominous sign and led to the founding of the Nemean Games.
-
D.
Ochimus
Ochimus is a figure in Greek mythology, known as a son of the sea nymph Rhode and associated with the early rulers of the island of Rhodes.
-
E.
Zethus
Zethus is a figure in Greek mythology, a son of Zeus and Antiope and twin brother of Amphion, known as a co-founder and ruler of the city of Thebes.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df9228088190bdd57a95d8671618 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96ba260b48190a5bde201ee3df69a |
completed | April 10, 2026, 9:29 p.m. |
Created at: April 8, 2026, 8:57 p.m.