Triple
T11864025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaine–Surrey |
E282235
|
entity |
| Predicate | borderDirectionFromCanada |
P27801
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Blaine–Surrey, borderDirectionFromCanada, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionFromCanada Context triple: [Blaine–Surrey, borderDirectionFromCanada, south]
-
A.
countryBorderDirection
chosen
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
borderWithUnitedStatesVia
Indicates that one entity shares a border with the United States specifically through or along the second entity (such as a body of water, territory, or region).
-
D.
hasBorderLengthWithCanada_km
Indicates the length, in kilometers, of the land or maritime border that an entity shares with Canada.
-
E.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.