Triple
T17427473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bois du Cazier |
E423775
|
entity |
| Predicate | numberOfDeathsIn1956Disaster |
P63692
|
FINISHED |
| Object | 262 |
—
|
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: 262 | Statement: [Bois du Cazier, numberOfDeathsIn1956Disaster, 262]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDeathsIn1956Disaster Context triple: [Bois du Cazier, numberOfDeathsIn1956Disaster, 262]
-
A.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
B.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
C.
numberOfVictimsConfirmed
Indicates the confirmed count of victims associated with an event, incident, or situation.
-
D.
numberOfSuspectedVictims
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
-
E.
numberOfVictimsKilled
chosen
Indicates the count of victims who were killed as a result of the referenced event or action.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fdc1348190985db52c8c74c394 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.