Triple
T14208231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Magnesia |
E352156
|
entity |
| Predicate | SeleucidArmyFeatures |
P6154
|
FINISHED |
| Object | war elephants |
—
|
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: war elephants | Statement: [Battle of Magnesia, SeleucidArmyFeatures, war elephants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SeleucidArmyFeatures Context triple: [Battle of Magnesia, SeleucidArmyFeatures, war elephants]
-
A.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
B.
ParthianForceType
Indicates the type or classification of a military force associated with the Parthians.
-
C.
RomanArmyType
Indicates the specific organizational or functional category to which a Roman military force belongs (e.g., legion, auxiliary, navy).
-
D.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
imperialAssaultUnits
Indicates a relationship where certain military units are designated as specialized forces used to carry out assaults on behalf of an empire or imperial authority.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61fa8d24819092a8ec5d34c1c799 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:05 a.m.