Triple
T28039187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking Graben |
E708490
|
entity |
| Predicate | mainReservoirLithology |
P17895
|
FINISHED |
| Object | sandstone |
—
|
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: sandstone | Statement: [Viking Graben, mainReservoirLithology, sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReservoirLithology Context triple: [Viking Graben, mainReservoirLithology, sandstone]
-
A.
reservoirFormation
Indicates the process or result of creating, developing, or naturally forming a reservoir in a given location or geological context.
-
B.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
C.
lithologyVariation
Indicates variation in the rock or sediment type present within a geological unit or between compared geological units.
-
D.
lithologyAffected
Indicates that one lithology is influenced, altered, or impacted in some way by another geological process, material, or condition.
-
E.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:23 p.m.