Triple
T24106656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont–Quebec border |
E597243
|
entity |
| Predicate | hasBorderCommunity |
P28598
|
FINISHED |
| Object | Alburgh, Vermont |
—
|
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: Alburgh, Vermont | Statement: [Vermont–Quebec border, hasBorderCommunity, Alburgh, Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderCommunity Context triple: [Vermont–Quebec border, hasBorderCommunity, Alburgh, Vermont]
-
A.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
isBorderMunicipality
chosen
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
- 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_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. |
Created at: April 17, 2026, 11:01 p.m.