Triple
T1942000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feldspar Brook |
E41574
|
entity |
| Predicate | isHeadwaterOf |
P415
|
FINISHED |
| Object | Hudson River system |
—
|
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: Hudson River system | Statement: [Feldspar Brook, isHeadwaterOf, Hudson River system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeadwaterOf Context triple: [Feldspar Brook, isHeadwaterOf, Hudson River system]
-
A.
tributary
chosen
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
B.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
C.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
D.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
E.
hydrologicallyConnectedTo
Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.