Triple
T3870863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont–New Hampshire border |
E91980
|
entity |
| Predicate | northTerminusRegion |
P51585
|
FINISHED |
| Object | near the Canadian border |
—
|
LITERAL 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: near the Canadian border | Statement: [Vermont–New Hampshire border, northTerminusRegion, near the Canadian border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northTerminusRegion Context triple: [Vermont–New Hampshire border, northTerminusRegion, near the Canadian border]
-
A.
northTerminusType
Indicates the type or nature of the northern endpoint or terminus of a route, line, or similar linear feature.
-
B.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
C.
northernTerminusState
Indicates that a location or route has its northern endpoint or terminus within the specified state.
-
D.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
E.
terminusCountryNorth
Indicates the country in which the northern terminus (end point) of something, such as a route or line, is located.
- F. None of above. chosen
Provenance (4 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec54b0848190a8d4a0e4df7b6227 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.