Triple
T6467199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 London bombings |
E142259
|
entity |
| Predicate | numberOfCivilianFatalities |
P34802
|
FINISHED |
| Object | 52 |
—
|
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: 52 | Statement: [2005 London bombings, numberOfCivilianFatalities, 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCivilianFatalities Context triple: [2005 London bombings, numberOfCivilianFatalities, 52]
-
A.
casualtiesCiviliansKilled
chosen
Indicates that the relationship records the number of civilian deaths resulting from a specific event or action.
-
B.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
C.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
D.
civilianImpact
Indicates the extent to which an action, event, or situation affects civilians, especially in terms of harm, disruption, or other consequences.
-
E.
fatalitiesCategory
Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a12ccf481908f71f888cd744b64 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.