Triple
T777592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bog Brook Reservoir |
E16423
|
entity |
| Predicate | bodyOfWaterType |
P1011
|
FINISHED |
| Object | freshwater 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: freshwater reservoir | Statement: [Bog Brook Reservoir, bodyOfWaterType, freshwater reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyOfWaterType Context triple: [Bog Brook Reservoir, bodyOfWaterType, freshwater reservoir]
-
A.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterMassType
Indicates the classification of a body of water according to its physical or compositional type.
-
D.
connectsBodyOfWater
Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
-
E.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.