Triple
T30619490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shedgum |
E779406
|
entity |
| Predicate | reservoirRockType |
P1326
|
FINISHED |
| Object | carbonate |
—
|
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 | Statement: [Shedgum, reservoirRockType, carbonate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirRockType Context triple: [Shedgum, reservoirRockType, carbonate]
-
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.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
C.
reservoirFormation
Indicates the process or result of creating, developing, or naturally forming a reservoir in a given location or geological context.
-
D.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
E.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689ed5b9c81909976d061f71d782a |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.