Triple
T13358998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent coalfield |
E318772
|
entity |
| Predicate | lastDeepMineClosed |
P17533
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Kent coalfield, lastDeepMineClosed, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastDeepMineClosed Context triple: [Kent coalfield, lastDeepMineClosed, 1989]
-
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.
hasOpenPitMine
Indicates that an entity operates, contains, or is associated with an open-pit mining site.
-
C.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
D.
miningActivityEnd
chosen
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
E.
closedAsCommercialMine
Indicates that a mine ceased operations specifically as a commercial mining enterprise.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.