Triple
T296503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Coventry |
E6102
|
entity |
| Predicate | buildingsDamagedOrDestroyed |
P1583
|
FINISHED |
| Object | more than 43,000 houses |
—
|
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: more than 43,000 houses | Statement: [bombing of Coventry, buildingsDamagedOrDestroyed, more than 43,000 houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingsDamagedOrDestroyed Context triple: [bombing of Coventry, buildingsDamagedOrDestroyed, more than 43,000 houses]
-
A.
buildingsDestroyed
chosen
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
-
B.
mainCityDestroyed
Indicates that the primary or central city associated with an entity has been destroyed.
-
C.
cityBombed
Indicates that a particular city was subjected to a bombing attack.
-
D.
wasBombedOn
Indicates that a location or target experienced a bombing event at a specific time or date.
-
E.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
- 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.