Triple
T27282335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jalula |
E688370
|
entity |
| Predicate | SasanianCommanderTitle |
P2084
|
FINISHED |
| Object | Mihran of Ray |
—
|
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: Mihran of Ray | Statement: [Battle of Jalula, SasanianCommanderTitle, Mihran of Ray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SasanianCommanderTitle Context triple: [Battle of Jalula, SasanianCommanderTitle, Mihran of Ray]
-
A.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
B.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
C.
EthiopianCommanderTitle
Indicates that an entity holds or is associated with a military or command rank/title specific to Ethiopian forces or history.
-
D.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
E.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
- F. None of above.
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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62751c1fc81908d1efe3eb9a2aa2b |
completed | May 2, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:08 a.m.