Triple
T32208141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore Basin |
E822726
|
entity |
| Predicate | reservoirRocks |
P114524
|
FINISHED |
| Object | carbonates |
—
|
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: carbonates | Statement: [Ardmore Basin, reservoirRocks, carbonates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirRocks Context triple: [Ardmore Basin, reservoirRocks, carbonates]
-
A.
reservoirFormation
Indicates the process or result of creating, developing, or naturally forming a reservoir in a given location or geological context.
-
B.
reservoirRock
chosen
Indicates that one entity functions as a porous and permeable rock formation capable of storing and transmitting fluids (such as hydrocarbons or water) for another entity.
-
C.
petroleumSystemElement
Indicates a relationship where something functions as a component or constituent element within a petroleum system.
-
D.
enhancedOilRecoveryTechnique
Indicates a technique or method used to increase the amount of oil that can be extracted from a reservoir beyond what primary and secondary recovery methods achieve.
-
E.
inReservoirSystem
Indicates that one entity is part of, contained within, or managed by a particular reservoir system.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb8fea508190b1e1b41b8fbded49 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.