Triple
T31639665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mount Gindarus |
E807408
|
entity |
| Predicate | aimOfRomanSide |
P47691
|
FINISHED |
| Object | expel Parthian forces from Roman Syria |
—
|
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: expel Parthian forces from Roman Syria | Statement: [Battle of Mount Gindarus, aimOfRomanSide, expel Parthian forces from Roman Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfRomanSide Context triple: [Battle of Mount Gindarus, aimOfRomanSide, expel Parthian forces from Roman Syria]
-
A.
aimOfRome
chosen
Indicates that something is the goal, purpose, or intended objective of Rome.
-
B.
estimatedRomanForces
Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
-
C.
aimOfByzantines
Indicates the goal or objective pursued by the Byzantines in a given context.
-
D.
stanceTowardRome
Indicates the nature or attitude of an entity’s position or policy in relation to Rome.
-
E.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:49 p.m.