Triple
T36015133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chyulu Hills aquifer |
E1041816
|
entity |
| Predicate | hydrogeologicalType |
P37190
|
FINISHED |
| Object | volcanic aquifer |
—
|
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: volcanic aquifer | Statement: [Chyulu Hills aquifer, hydrogeologicalType, volcanic aquifer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydrogeologicalType Context triple: [Chyulu Hills aquifer, hydrogeologicalType, volcanic aquifer]
-
A.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
B.
aquiferType
chosen
Indicates the classification or category of an aquifer based on its hydrogeologic characteristics or behavior.
-
C.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
D.
geomorphicType
Indicates the classification of a geographic feature based on its landform or geomorphic characteristics.
-
E.
aquiferMaterial
Indicates that one entity serves as the material or geologic substance composing or characterizing an aquifer associated with another 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acb62b748190891abc766a339b23 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.