Triple
T38150254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River estuary |
E952731
|
entity |
| Predicate | hasSourceWater |
P4102
|
FINISHED |
| Object | freshwater from upper Hudson River |
—
|
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 from upper Hudson River | Statement: [Hudson River estuary, hasSourceWater, freshwater from upper Hudson River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceWater Context triple: [Hudson River estuary, hasSourceWater, freshwater from upper Hudson River]
-
A.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
B.
waterSourceType
Indicates the kind or category of source from which water is obtained.
-
C.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
D.
hasWaterAvailability
Indicates that an entity has access to or is supplied with a certain amount or level of water.
-
E.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:21 p.m.