Triple
T11199281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Carrhae |
E264996
|
entity |
| Predicate | RomanForceType |
P86508
|
FINISHED |
| Object | legionaries |
—
|
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: legionaries | Statement: [Battle of Carrhae, RomanForceType, legionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanForceType Context triple: [Battle of Carrhae, RomanForceType, legionaries]
-
A.
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.
-
B.
SpanishForceComponent
Indicates that an entity functions as a component or sub-unit of a Spanish military or armed force.
-
C.
RomanArmyType
chosen
Indicates the specific organizational or functional category to which a Roman military force belongs (e.g., legion, auxiliary, navy).
-
D.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
E.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.