Triple
T17427482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bois du Cazier |
E423775
|
entity |
| Predicate | causeOf1956Disaster |
P127418
|
FINISHED |
| Object | underground fire |
—
|
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: underground fire | Statement: [Bois du Cazier, causeOf1956Disaster, underground fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOf1956Disaster Context triple: [Bois du Cazier, causeOf1956Disaster, underground fire]
-
A.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
B.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
causeOfShipwreck
Indicates the factor, event, or condition that directly led to a shipwreck occurring.
-
D.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.