Triple
T26180029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roundout Reservoir |
E654648
|
entity |
| Predicate | environmentalZone |
P161653
|
FINISHED |
| Object | protected watershed area |
—
|
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: protected watershed area | Statement: [Roundout Reservoir, environmentalZone, protected watershed area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentalZone Context triple: [Roundout Reservoir, environmentalZone, protected watershed area]
-
A.
environmentalConstraint
Indicates that an entity is subject to limitations, conditions, or restrictions imposed by its surrounding physical, ecological, or environmental context.
-
B.
borderingEnvironment
Indicates that one environment or habitat lies directly adjacent to and shares a boundary with another environment.
-
C.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
D.
rangeEnvironment
Indicates that an entity operates or exists within a specified environmental range or conditions.
-
E.
environmentSubtype
chosen
Indicates that one environment is a more specific subtype or category within another, more general environment.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 8:39 p.m.