Triple
T17220415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pompton River |
E417963
|
entity |
| Predicate | receivesTributary |
P415
|
FINISHED |
| Object | Wanaque River |
—
|
NE NERFINISHED |
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: Wanaque River | Statement: [Pompton River, receivesTributary, Wanaque River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesTributary Context triple: [Pompton River, receivesTributary, Wanaque River]
-
A.
hasTributaryType
Indicates that one watercourse is classified as a specific type of tributary in relation to another water body.
-
B.
containsTributariesOf
Indicates that one water body or drainage system includes within it the tributary streams or rivers of another.
-
C.
tributary
chosen
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
D.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
E.
tributarySide
Indicates the side (e.g., left or right bank) of a main watercourse on which a tributary joins it.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddd52d4819098b51d55e063c8ab |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.