Triple
T6961158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakken formation region |
E161370
|
entity |
| Predicate | majorDevelopmentBegan |
P10779
|
FINISHED |
| Object | mid-2000s |
—
|
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: mid-2000s | Statement: [Bakken formation region, majorDevelopmentBegan, mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDevelopmentBegan Context triple: [Bakken formation region, majorDevelopmentBegan, mid-2000s]
-
A.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
B.
significantDevelopmentUnder
Indicates that one entity has undergone a major or notable development, change, or advancement under the influence, authority, or conditions provided by another entity.
-
C.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
D.
laterDevelopments
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
E.
developedAt
Indicates the place or location where something was created, built, or developed.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daeee4d48190b078beeebb0053f4 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.