Triple
T28983542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Snake River Plain Aquifer |
E734614
|
entity |
| Predicate | aquiferMaterial |
P166085
|
FINISHED |
| Object | fractured basalt flows |
—
|
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: fractured basalt flows | Statement: [Eastern Snake River Plain Aquifer, aquiferMaterial, fractured basalt flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aquiferMaterial Context triple: [Eastern Snake River Plain Aquifer, aquiferMaterial, fractured basalt flows]
-
A.
aquiferType
Indicates the classification or category of an aquifer based on its hydrogeologic characteristics or behavior.
-
B.
formsAquifers
Indicates that something creates, develops, or contributes to the formation of aquifers as groundwater-bearing geological structures.
-
C.
cliffMaterial
Indicates that a cliff is composed of or primarily made from a specified material.
-
D.
aquiferRole
Indicates the functional role or purpose that an entity has in relation to an aquifer within a hydrological or geological context.
-
E.
foundationMaterial
Indicates the material from which the foundation or base of something is constructed.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee617488190ab8ce4f73be9c651 |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:12 a.m.