Triple
T7021366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonauts |
E162831
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Telamon |
E291382
|
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: Telamon | Statement: [Argonauts, hasMember, Telamon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telamon Context triple: [Argonauts, hasMember, Telamon]
-
A.
Telamon
chosen
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.
-
B.
Agenor
Agenor is a figure in Greek mythology, often portrayed as a Phoenician king and ancestor of several notable mythic characters, including Semele.
-
C.
Aeacus
Aeacus is a just and pious king from Greek mythology who ruled the island of Aegina and later became one of the three judges of the dead in the underworld.
-
D.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
-
E.
Temenus of Argos
Temenus of Argos is a legendary Heraclid king of Argos in Greek mythology, regarded as an ancestor of the Argead dynasty of Macedon.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1ec34a48190b64cafb94e2f8706 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7885104e881909be62c2eb12e0bcf |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:35 p.m.