Triple
T24106639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont–Quebec border |
E597243
|
entity |
| Predicate | hasBorderTownOnCanadianSide |
P155088
|
FINISHED |
| Object | Stanstead, Quebec |
—
|
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: Stanstead, Quebec | Statement: [Vermont–Quebec border, hasBorderTownOnCanadianSide, Stanstead, Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTownOnCanadianSide Context triple: [Vermont–Quebec border, hasBorderTownOnCanadianSide, Stanstead, Quebec]
-
A.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
-
C.
hasBorderLengthWithCanada_km
Indicates the length, in kilometers, of the land or maritime border that an entity shares with Canada.
-
D.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
E.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de170ee88190a6d57482651f7da9 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:01 p.m.