Triple
T24261471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lot coal basin |
E604713
|
entity |
| Predicate | currentMiningStatus |
P29776
|
FINISHED |
| Object | mining ceased |
—
|
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: mining ceased | Statement: [Lot coal basin, currentMiningStatus, mining ceased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMiningStatus Context triple: [Lot coal basin, currentMiningStatus, mining ceased]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
miningAllowed
Indicates that performing mining activities is permitted under the relevant rules or conditions.
-
C.
miningStarted
Indicates that the process of extracting resources from a source or site has begun.
-
D.
miningHistory
chosen
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
E.
hasMiningActivityType
Indicates that an entity is associated with a specific type or category of mining activity.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6727388190862e3ce09c372c70 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.