Triple
T11157256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajax |
E263942
|
entity |
| Predicate | epithet |
P743
|
FINISHED |
| Object | Ajax son of Telamon |
E907363
|
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: Ajax son of Telamon | Statement: [Ajax, epithet, Ajax son of Telamon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ajax son of Telamon Context triple: [Ajax, epithet, Ajax son of Telamon]
-
A.
Telamonian Ajax
chosen
Telamonian Ajax is a towering Greek hero of the Trojan War in Homeric epic, renowned for his immense strength, courage, and steadfast defense of the Achaean forces.
-
B.
Perseus (son of Nestor)
Perseus is a minor figure in Greek mythology, known primarily as one of the many sons of the Pylian king Nestor.
-
C.
Telamon
Telamon is a hero in Greek mythology, best known as the father of Ajax the Great and a companion of Heracles in several of his exploits.
-
D.
Antilochus
Antilochus is a figure in Greek mythology, a son of Nestor renowned for his bravery and close friendship with Achilles during the Trojan War.
-
E.
Idomeneus
Idomeneus is a legendary Cretan king and warrior in Greek mythology, renowned as one of the prominent Greek leaders and fighters in the Trojan War.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e87fe9a881909540ecc4ed9b6b9f |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e496c152a081909c6ad8b2a6e41927 |
completed | April 19, 2026, 8:48 a.m. |
Created at: April 8, 2026, 9:28 p.m.