Triple
T17768105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware River watershed |
E443562
|
entity |
| Predicate | includesTributary |
P165
|
FINISHED |
| Object | Beaver Brook |
—
|
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: Beaver Brook | Statement: [Delaware River watershed, includesTributary, Beaver Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beaver Brook Context triple: [Delaware River watershed, includesTributary, Beaver Brook]
-
A.
Beaver Brook
Beaver Brook is a stream in the town of Dracut, Massachusetts, that forms part of the local watershed and natural landscape.
-
B.
Beaver Brook
chosen
Beaver Brook is a smaller stream in New Jersey that feeds into the Musconetcong River as part of the region’s freshwater watershed.
-
C.
Beaver Brook
Beaver Brook is a stream in southern New Hampshire that flows through the town of Pelham and surrounding communities.
-
D.
Salmon Brook
Salmon Brook is a small tributary stream in north London, England, that flows through suburban areas before joining the River Lea.
-
E.
Mashamoquet Brook
Mashamoquet Brook is a small watercourse in northeastern Connecticut known for flowing through and giving its name to Mashamoquet Brook State Park.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fd8aa081909c8ee9264af15c69 |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 10:11 a.m.