Triple
T2874919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Branch Croton River |
E56853
|
entity |
| Predicate | watercourseUses |
P30340
|
FINISHED |
| Object | municipal water supply |
—
|
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: municipal water supply | Statement: [West Branch Croton River, watercourseUses, municipal water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseUses Context triple: [West Branch Croton River, watercourseUses, municipal water supply]
-
A.
waterwayFunction
chosen
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
B.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
C.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
D.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
E.
waterQualityUse
Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.