Triple
T21312633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stampede Reservoir |
E525380
|
entity |
| Predicate | surfaceWaterBodyType |
P1011
|
FINISHED |
| Object | reservoir |
—
|
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: reservoir | Statement: [Stampede Reservoir, surfaceWaterBodyType, reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterBodyType Context triple: [Stampede Reservoir, surfaceWaterBodyType, reservoir]
-
A.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
B.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
C.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
D.
hydronymType
Indicates the specific type or category of a water-related geographical name (e.g., river, lake, sea) associated with a hydronym.
-
E.
waterMassType
Indicates the classification of a body of water according to its physical or compositional type.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcb45f08190a9bcaa366964a2cb |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:25 p.m.