Triple
T22598568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Mountain Sandstone |
E574749
|
entity |
| Predicate | formsAquifers |
P148878
|
FINISHED |
| Object | limited fractured-rock aquifers |
—
|
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: limited fractured-rock aquifers | Statement: [Table Mountain Sandstone, formsAquifers, limited fractured-rock aquifers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsAquifers Context triple: [Table Mountain Sandstone, formsAquifers, limited fractured-rock aquifers]
-
A.
aquiferType
Indicates the classification or category of an aquifer based on its hydrogeologic characteristics or behavior.
-
B.
aquiferRole
Indicates the functional role or purpose that an entity has in relation to an aquifer within a hydrological or geological context.
-
C.
hasAquifer
Indicates that one entity possesses, contains, or overlies an aquifer associated with it.
-
D.
collectsGroundwaterFor
Indicates a relationship where one entity gathers or channels groundwater for the benefit or use of another entity.
-
E.
reservoirFormation
Indicates the process or result of creating, developing, or naturally forming a reservoir in a given location or geological context.
- F. None of above. chosen
Provenance (4 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626aa0808190a43e65f6aaabfeb4 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:50 p.m.