Triple
T5632163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvic |
E147857
|
entity |
| Predicate | waterExtraction |
P4102
|
FINISHED |
| Object | deep 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: deep volcanic aquifer | Statement: [Volvic, waterExtraction, deep volcanic aquifer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterExtraction Context triple: [Volvic, waterExtraction, deep volcanic aquifer]
-
A.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterExposure
Indicates that one entity is subjected to contact with water from another source or environment.
-
C.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
D.
waterExchangeThrough
Indicates a relationship where water is transferred or shared between entities through a specific medium, pathway, or mechanism.
-
E.
waterDivertedFrom
Indicates that water is intentionally redirected or channeled away from one source, path, or location to another.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.