Triple
T13740384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British coal industry |
E330069
|
entity |
| Predicate | nearEndOfDeepMining |
P43866
|
FINISHED |
| Object | closure of Kellingley Colliery in 2015 |
—
|
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: closure of Kellingley Colliery in 2015 | Statement: [British coal industry, nearEndOfDeepMining, closure of Kellingley Colliery in 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearEndOfDeepMining Context triple: [British coal industry, nearEndOfDeepMining, closure of Kellingley Colliery in 2015]
-
A.
miningActivityEnd
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
B.
undergroundMiningContinuedUntil
chosen
Indicates that the activity of underground mining persisted up to a specified time or event.
-
C.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
D.
miningSite
Indicates a location where mining activities or mineral extraction operations take place.
-
E.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0206a4b88190a60914e2b43e54f9 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.