Triple
T1496377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberjona River |
E29695
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Horn Pond Brook |
E180184
|
NE 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: Horn Pond Brook | Statement: [Aberjona River, hasTributary, Horn Pond Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horn Pond Brook Context triple: [Aberjona River, hasTributary, Horn Pond Brook]
-
A.
Horn Pond Brook
chosen
Horn Pond Brook is a small stream in Massachusetts that serves as a tributary within the greater Mystic River watershed system.
-
B.
Wedge Pond Brook
Wedge Pond Brook is a small stream in Massachusetts that forms part of the Mystic River watershed.
-
C.
Browns Pond Brook
Browns Pond Brook is a small stream in Massachusetts that serves as one of the tributaries feeding into the Saugus River.
-
D.
Bog Brook
Bog Brook is a stream in New York State that serves as a primary feeder to the Bog Brook Reservoir within the New York City water supply system.
-
E.
Porter Brook
Porter Brook is a small urban river running through Sheffield, England, historically important for powering the city’s early industry.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6ec70c48190a94f6e1002848eae |
completed | March 1, 2026, 11:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58b487c08190bb2b1c259bd39db0 |
completed | March 8, 2026, 11:08 a.m. |
Created at: March 1, 2026, 8:12 p.m.