Triple
T3626257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gaugamela |
E76845
|
entity |
| Predicate | PersianForcesIncluded |
P46576
|
FINISHED |
| Object | war chariots |
—
|
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 chariots | Statement: [Battle of Gaugamela, PersianForcesIncluded, war chariots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PersianForcesIncluded Context triple: [Battle of Gaugamela, PersianForcesIncluded, war chariots]
-
A.
PersianForceComponent
chosen
Indicates that an entity functions as a constituent unit or sub-force within a larger Persian military force or formation.
-
B.
PersianCommander
Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
-
C.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
E.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dc011c8190a6596f4b483fb078 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.