Triple
T25202765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williston Basin |
E631163
|
entity |
| Predicate | peakDevelopmentPhase |
P22203
|
FINISHED |
| Object | post-2000 Bakken shale boom |
—
|
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: post-2000 Bakken shale boom | Statement: [Williston Basin, peakDevelopmentPhase, post-2000 Bakken shale boom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDevelopmentPhase Context triple: [Williston Basin, peakDevelopmentPhase, post-2000 Bakken shale boom]
-
A.
mainDevelopmentPeriod
chosen
Indicates the primary time span during which the main development or formation of something took place.
-
B.
developmentPhaseName
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
C.
partOfDevelopment
Indicates that one entity is a component, phase, or contributing element within the overall development process of another entity.
-
D.
underDevelopment
Indicates that something is currently being created, improved, or worked on and is not yet in its final or completed state.
-
E.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b904f48190be6513788f89c6a9 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:51 p.m.