Triple
T1857387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware system |
E41734
|
entity |
| Predicate | usesWatershed |
P25275
|
FINISHED |
| Object | Delaware River watershed |
—
|
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: Delaware River watershed | Statement: [Delaware system, usesWatershed, Delaware River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWatershed Context triple: [Delaware system, usesWatershed, Delaware River watershed]
-
A.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
B.
formsWatershedFor
Indicates that one geographic feature or area serves as the drainage boundary or catchment area that collects precipitation and channels it into another water body or region.
-
C.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
D.
hasWatershedUse
chosen
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
E.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the drainage system.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.