Triple
T25444865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raglan’s army |
E637604
|
entity |
| Predicate | hasCasualtiesIn |
P110385
|
FINISHED |
| Object | Crimean War |
—
|
NE NERFINISHED |
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: Crimean War | Statement: [Raglan’s army, hasCasualtiesIn, Crimean War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCasualtiesIn Context triple: [Raglan’s army, hasCasualtiesIn, Crimean War]
-
A.
hasChildCasualties
Indicates that an event, incident, or situation resulted in casualties specifically involving children.
-
B.
hasCasualtiesLevel
Indicates the severity or extent of casualties associated with an event, incident, or situation.
-
C.
sustainedHeavyCasualtiesAt
chosen
Indicates that an entity experienced a large number of serious losses (e.g., deaths or injuries) at a specific location or during a specific event.
-
D.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
E.
casualtiesIncluded
Indicates that the referenced count or report of casualties explicitly includes the specified individuals or groups.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 2 p.m.