Triple
T27229201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litchfield, New Hampshire |
E682103
|
entity |
| Predicate | borderedByRiverOnWest |
P180178
|
FINISHED |
| Object | Merrimack 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: Merrimack River | Statement: [Litchfield, New Hampshire, borderedByRiverOnWest, Merrimack River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByRiverOnWest Context triple: [Litchfield, New Hampshire, borderedByRiverOnWest, Merrimack River]
-
A.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
B.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
C.
riverBankOnWest
chosen
Indicates that the river’s bank is located on the western side relative to a referenced position or feature.
-
D.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
E.
boundaryTypeWest
Indicates the type or nature of the boundary that exists on the western side of an entity or area.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 9:45 a.m.