Triple
T296500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Coventry |
E6102
|
entity |
| Predicate | civilianDeaths |
P1785
|
FINISHED |
| Object | around 568 people |
—
|
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: around 568 people | Statement: [bombing of Coventry, civilianDeaths, around 568 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilianDeaths Context triple: [bombing of Coventry, civilianDeaths, around 568 people]
-
A.
deathToll
chosen
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
B.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
C.
civilianImpact
Indicates the extent to which an action, event, or situation affects civilians, especially in terms of harm, disruption, or other consequences.
-
D.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
E.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.