Triple
T16575137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkoma Basin |
E402689
|
entity |
| Predicate | hasHydrocarbonTraps |
P124113
|
FINISHED |
| Object | structural traps |
—
|
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: structural traps | Statement: [Arkoma Basin, hasHydrocarbonTraps, structural traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydrocarbonTraps Context triple: [Arkoma Basin, hasHydrocarbonTraps, structural traps]
-
A.
hydrocarbonPotential
Indicates the degree to which a geological unit or material is capable of generating, containing, or yielding hydrocarbons such as oil or natural gas.
-
B.
hasHydrocarbonLakes
Indicates that the subject possesses or contains lakes composed primarily of liquid hydrocarbons rather than water.
-
C.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
D.
hasHydrocarbonSeas
Indicates that an entity possesses or is characterized by the presence of seas composed primarily of liquid hydrocarbons.
-
E.
discoveredAsPetroleumPlay
Indicates that the subject was identified or recognized specifically as a viable petroleum exploration or production opportunity.
- F. None of above. chosen
Provenance (4 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595bbbbc8190b023f4872908c031 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.