Triple
T15032657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin |
E378390
|
entity |
| Predicate | encounters |
P13259
|
FINISHED |
| Object | King Agamemnon |
E102222
|
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: King Agamemnon | Statement: [Kevin, encounters, King Agamemnon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King Agamemnon Context triple: [Kevin, encounters, King Agamemnon]
-
A.
Agamemnon
chosen
Agamemnon is the legendary king of Mycenae and commander of the Greek forces in the Trojan War in Greek mythology.
-
B.
Ἀγαμέμνων
Ἀγαμέμνων is the legendary king of Mycenae and commander of the Greek forces in the Trojan War in ancient Greek mythology.
-
C.
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.
-
D.
Sthenelus of Mycenae
Sthenelus of Mycenae is a figure in Greek mythology, a Mycenaean prince known primarily as the son of King Eurystheus.
-
E.
King of Sparta
Archidamus III was a 4th-century BC Spartan king known for his military leadership during the Peloponnesian War’s aftermath and conflicts with Thebes and 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e3a7c8819081f26c2435c1bcb2 |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9ddb46888190b1d2fe2992fc120b |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:59 a.m.