Triple
T32080897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raton Basin coal fields |
E819293
|
entity |
| Predicate | laterResourceDevelopment |
P13185
|
FINISHED |
| Object | coalbed methane |
—
|
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: coalbed methane | Statement: [Raton Basin coal fields, laterResourceDevelopment, coalbed methane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterResourceDevelopment Context triple: [Raton Basin coal fields, laterResourceDevelopment, coalbed methane]
-
A.
laterDevelopments
chosen
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
B.
developedResource
Indicates that an entity has created, produced, or otherwise brought into existence a particular resource.
-
C.
laterConstruction
Indicates that one construction event or structure occurred or was built after another in time.
-
D.
territorialDevelopment
Indicates the process or actions through which a geographic area is planned, organized, and transformed for social, economic, or infrastructural purposes.
-
E.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
- 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_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 1, 2026, 12:24 a.m.