Triple
T28039184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking Graben |
E708490
|
entity |
| Predicate | mainSourceRock |
P97391
|
FINISHED |
| Object | Kimmeridge Clay Formation equivalents |
—
|
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: Kimmeridge Clay Formation equivalents | Statement: [Viking Graben, mainSourceRock, Kimmeridge Clay Formation equivalents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSourceRock Context triple: [Viking Graben, mainSourceRock, Kimmeridge Clay Formation equivalents]
-
A.
reservoirRock
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.
-
B.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
-
C.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
D.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
E.
rockUnit
chosen
Indicates a relationship where an entity is classified as, or associated with, a particular geological rock unit.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 8:23 p.m.