Triple
T12770399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vimy Ridge |
E305232
|
entity |
| Predicate | battleCasualtiesAllied |
P17247
|
FINISHED |
| Object | over 10,000 Canadian casualties |
—
|
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: over 10,000 Canadian casualties | Statement: [Vimy Ridge, battleCasualtiesAllied, over 10,000 Canadian casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCasualtiesAllied Context triple: [Vimy Ridge, battleCasualtiesAllied, over 10,000 Canadian casualties]
-
A.
casualtiesAllied
chosen
Indicates the number or extent of losses (killed, wounded, or missing) suffered by allied forces in a conflict or incident.
-
B.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
C.
troopStrengthAlliedApprox
Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
-
D.
militaryCasualtiesSide
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
E.
casualtiesUnion
Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df4b36c81909bcc913dd5e535f8 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.