Triple
T9281929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Barrosa |
E223088
|
entity |
| Predicate | alliedComposition |
P17251
|
FINISHED |
| Object | British and Spanish coalition forces |
—
|
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: British and Spanish coalition forces | Statement: [Battle of Barrosa, alliedComposition, British and Spanish coalition forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedComposition Context triple: [Battle of Barrosa, alliedComposition, British and Spanish coalition forces]
-
A.
alliedForcesComposition
chosen
Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
-
B.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
C.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
D.
alliedDesignation
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
E.
alliedGroups
Indicates that two or more groups are formally cooperating or aligned in support of shared goals or interests.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081c2b048190aa6930de3bf2f87f |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.