Triple
T24571557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arigna coal mining area |
E607974
|
entity |
| Predicate | lastMineClosed |
P152124
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Arigna coal mining area, lastMineClosed, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMineClosed Context triple: [Arigna coal mining area, lastMineClosed, 1990]
-
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.
closedAsCommercialMine
Indicates that a mine ceased operations specifically as a commercial mining enterprise.
-
C.
operatedAsMineUntil
chosen
Indicates that an entity functioned in the capacity of a mine up to a specified point in time.
-
D.
closedAsMine
Indicates that an issue or report was closed because it was determined to be a duplicate of one already owned or previously handled by the closer.
-
E.
closedAsMint
Indicates that an issue, report, or request was resolved and marked as valid or correct in its original form, without requiring changes.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9257ccc81908efcd9d047772492 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.