Triple
T5852593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandown, New Hampshire |
E130070
|
entity |
| Predicate | hasWaterBody |
P165
|
FINISHED |
| Object |
Little River
Little River is a small waterway in southeastern New Hampshire that flows through the town of Sandown and its surrounding area.
|
E830760
|
NE FINISHED |
How this triple was built (4 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: Little River | Statement: [Sandown, New Hampshire, hasWaterBody, Little River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Little River Context triple: [Sandown, New Hampshire, hasWaterBody, Little River]
-
A.
Little River
Little River is a small waterway flowing through the town of Redding in Fairfield County, Connecticut.
-
B.
Little River
Little River is a scenic waterway in eastern Tennessee known for flowing through the Great Smoky Mountains and offering popular spots for fishing, tubing, and outdoor recreation.
-
C.
Little River
Little River is a waterway in Durham County, North Carolina, that serves as an important local stream and reservoir source for the surrounding communities.
-
D.
Little River
Little River is a small waterway in North Dakota, United States, more commonly known as the Park River.
-
E.
Little River
Little River is a small coastal waterway in Massachusetts known for surrounding Monomoscoy Island and connecting to the region’s tidal estuaries.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Little River Triple: [Sandown, New Hampshire, hasWaterBody, Little River]
Generated description
Little River is a small waterway in southeastern New Hampshire that flows through the town of Sandown and its surrounding area.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Little River Target entity description: Little River is a small waterway in southeastern New Hampshire that flows through the town of Sandown and its surrounding area.
-
A.
Little River
Little River is a small urban waterway in Massachusetts that flows through the Alewife Brook Reservation, contributing to its wetlands and wildlife habitat.
-
B.
Little River
Little River is a small coastal waterway in Massachusetts known for surrounding Monomoscoy Island and connecting to the region’s tidal estuaries.
-
C.
Little River
Little River is a waterway in Durham County, North Carolina, that serves as an important local stream and reservoir source for the surrounding communities.
-
D.
Little River
Little River is a smaller waterway in Vermont that feeds into the Winooski River and contributes to its watershed.
-
E.
Little River
Little River is a small waterway flowing through the town of Redding in Fairfield County, Connecticut.
- F. None of above. chosen
Provenance (5 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0355038008190bf38980349b533e2 |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2281e332c819093444685d37b9251 |
completed | April 5, 2026, 9:15 a.m. |
| NEDg | Description generation | batch_69d22968194c8190b919ed3ab2dcfc33 |
completed | April 5, 2026, 9:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d229d10dac81909f34a9977e6445a0 |
completed | April 5, 2026, 9:22 a.m. |
Created at: March 22, 2026, 3:55 p.m.