Triple
T34261274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Basin |
E879037
|
entity |
| Predicate | containsResourceType |
P3729
|
FINISHED |
| Object | conventional reservoirs |
—
|
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: conventional reservoirs | Statement: [Midland Basin, containsResourceType, conventional reservoirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsResourceType Context triple: [Midland Basin, containsResourceType, conventional reservoirs]
-
A.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
B.
appliesToResourceType
Indicates that a rule, condition, or operation is specifically targeted at and relevant for a particular type or category of resource.
-
C.
isResourceFor
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
D.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 1, 2026, 1:56 a.m.