Triple
T29036642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Afdera |
E737878
|
entity |
| Predicate | surfaceWaterSource |
P11699
|
FINISHED |
| Object | groundwater inflow |
—
|
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: groundwater inflow | Statement: [Lake Afdera, surfaceWaterSource, groundwater inflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterSource Context triple: [Lake Afdera, surfaceWaterSource, groundwater inflow]
-
A.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
B.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
C.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
E.
waterSourceType
chosen
Indicates the kind or category of source from which water is obtained.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:58 a.m.