Triple
T36121377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tithraustes |
E1044750
|
entity |
| Predicate | afterKillingTissaphernes |
P184710
|
FINISHED |
| Object | assumed command in western Asia Minor |
—
|
LITERAL 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: assumed command in western Asia Minor | Statement: [Tithraustes, afterKillingTissaphernes, assumed command in western Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterKillingTissaphernes Context triple: [Tithraustes, afterKillingTissaphernes, assumed command in western Asia Minor]
-
A.
aftermathOfCarrhae
Indicates the state, events, or consequences that occurred as a result of the Battle of Carrhae.
-
B.
resultOfAssyrianCampaign
Indicates that something occurs as a consequence or outcome of a specific Assyrian military campaign.
-
C.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
D.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
E.
combatOutcomeWithTheseus
Indicates the result or consequence of a combat encounter involving Theseus and another entity.
- F. None of above. chosen
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.