Triple
T33820054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powder River Basin |
E866803
|
entity |
| Predicate | coalSeam |
P77077
|
FINISHED |
| Object | Wyodak coal seam |
—
|
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: Wyodak coal seam | Statement: [Powder River Basin, coalSeam, Wyodak coal seam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalSeam Context triple: [Powder River Basin, coalSeam, Wyodak coal seam]
-
A.
coalType
Indicates the specific kind or classification of coal associated with an entity.
-
B.
coalMinedFrom
Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
-
C.
isCoalBearing
Indicates that the subject contains or is associated with coal deposits or coal-bearing formations.
-
D.
coalMeasure
chosen
Indicates that something is a geological coal-bearing stratum or formation within the coal measures sequence.
-
E.
coalTypeMined
Indicates that a particular type of coal is extracted or produced through mining at a given location or by a given agent.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fffb87108190b3e02be4678bdc73 |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.