Triple
T36342868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravensdale mine explosion of 1915 |
E894976
|
entity |
| Predicate | primaryFuelMined |
P204830
|
FINISHED |
| Object | bituminous coal |
—
|
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: bituminous coal | Statement: [Ravensdale mine explosion of 1915, primaryFuelMined, bituminous coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFuelMined Context triple: [Ravensdale mine explosion of 1915, primaryFuelMined, bituminous coal]
-
A.
miningScale
Indicates the relative size or intensity of a mining operation or activity.
-
B.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
C.
usedFusionFuel
Indicates that an entity employed a specified material or substance as fuel in a fusion process.
-
D.
secondaryFuel
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
E.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.