Triple
T6961174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakken formation region |
E161370
|
entity |
| Predicate | developmentTechnology |
P1482
|
FINISHED |
| Object | multi-stage hydraulic fracturing |
—
|
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: multi-stage hydraulic fracturing | Statement: [Bakken formation region, developmentTechnology, multi-stage hydraulic fracturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentTechnology Context triple: [Bakken formation region, developmentTechnology, multi-stage hydraulic fracturing]
-
A.
developmentCategory
Indicates the classification of an entity according to a particular stage, type, or area of development.
-
B.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
-
D.
technologyField
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
-
E.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented 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_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.