Triple
T9218056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells River, Vermont |
E221289
|
entity |
| Predicate | borderedByAcrossRiver |
P382
|
FINISHED |
| Object | Woodsville, New Hampshire |
—
|
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: Woodsville, New Hampshire | Statement: [Wells River, Vermont, borderedByAcrossRiver, Woodsville, New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByAcrossRiver Context triple: [Wells River, Vermont, borderedByAcrossRiver, Woodsville, New Hampshire]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
locatedAcrossRiverFrom
chosen
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
borderRiverContext
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
-
E.
borderingCountryAcrossLake
Indicates that two countries share a border that is defined or separated by a lake lying between them.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda0ae3d081908ff3f5dab52df5ae |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.