Triple
T28777428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerset coalfield area |
E726576
|
entity |
| Predicate | lastDeepMinesClosed |
P152124
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Somerset coalfield area, lastDeepMinesClosed, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastDeepMinesClosed Context triple: [Somerset coalfield area, lastDeepMinesClosed, 20th century]
-
A.
closedAsActiveMine
Indicates that a mine has been officially closed while still being recognized or managed as an active mining site in relevant records or systems.
-
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.
operatedAsMineUntil
chosen
Indicates that an entity functioned in the capacity of a mine up to a specified point in time.
-
D.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
-
E.
miningDisaster
Indicates a disastrous event occurring in the context of mining operations, typically involving significant damage, injury, or loss of life.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:18 a.m.