Triple
T17461392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darius III |
E425157
|
entity |
| Predicate | killedBy |
P4646
|
FINISHED |
| Object | Bessus |
—
|
NE NERFINISHED |
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: Bessus | Statement: [Darius III, killedBy, Bessus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bessus Context triple: [Darius III, killedBy, Bessus]
-
A.
Bessus
chosen
Bessus was a Persian noble and satrap who betrayed and murdered King Darius III during Alexander the Great’s conquest of the Achaemenid Empire.
-
B.
Tisiphonus
Tisiphonus was an ancient Greek ruler of Pherae in Thessaly, known as one of the successors in the turbulent dynastic line that followed the tyrant Jason of Pherae.
-
C.
Ariabignes
Ariabignes was a Persian prince and naval commander, son of King Darius I, who was killed while leading Persian forces during the Greco-Persian Wars.
-
D.
Bardylis
Bardylis was a powerful 4th-century BCE Illyrian king known for his military campaigns against Macedon and for significantly challenging Macedonian power before the rise of Philip II.
-
E.
Hystaspes
Hystaspes was a Persian nobleman of the Achaemenid dynasty, best known as the father of King Darius I of Persia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3c4cc8190937808e3272272c0 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:47 a.m.