Triple
T34261314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Basin Platform |
E879038
|
entity |
| Predicate | hasReservoirRock |
P114524
|
FINISHED |
| Object | carbonate rocks |
—
|
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: carbonate rocks | Statement: [Central Basin Platform, hasReservoirRock, carbonate rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservoirRock Context triple: [Central Basin Platform, hasReservoirRock, carbonate rocks]
-
A.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
-
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.
usesReservoir
Indicates that one entity draws upon, depends on, or operates using a particular reservoir as a resource or source.
-
D.
includesReservoir
Indicates that one entity contains or encompasses a reservoir as part of its structure, system, or area.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.