Triple
T32080879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raton Basin coal fields |
E819293
|
entity |
| Predicate | majorMiningCenters |
P183283
|
FINISHED |
| Object | Trinidad, Colorado |
—
|
NE NERFINISHED |
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: Trinidad, Colorado | Statement: [Raton Basin coal fields, majorMiningCenters, Trinidad, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorMiningCenters Context triple: [Raton Basin coal fields, majorMiningCenters, Trinidad, Colorado]
-
A.
mainMiningCenter
chosen
Indicates that a location serves as the primary site or hub for mining activities within a given context.
-
B.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
C.
relatedMiningDistrict
Indicates that one entity has an associative or contextual connection to a specific mining district.
-
D.
majorMine
Indicates that a mine is classified as a major or primary mining site, typically based on its scale, output, or importance.
-
E.
miningSite
Indicates a location where mining activities or mineral extraction operations take place.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 12:24 a.m.