Triple
T23403754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Reims (1814) |
E559575
|
entity |
| Predicate | coalitionForcesIncluded |
P39448
|
FINISHED |
| Object | Russian infantry |
—
|
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: Russian infantry | Statement: [Battle of Reims (1814), coalitionForcesIncluded, Russian infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionForcesIncluded Context triple: [Battle of Reims (1814), coalitionForcesIncluded, Russian infantry]
-
A.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
B.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
C.
coalitionCasualties
Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
-
D.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
E.
alliedForcesComposition
Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e16f9881908ea4bef465e3af11 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.