Triple
T9568403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niagara Centre |
E230846
|
entity |
| Predicate | borderingCountryContext |
P89848
|
FINISHED |
| Object | near Canada–United States 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 Canada–United States border | Statement: [Niagara Centre, borderingCountryContext, near Canada–United States border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCountryContext Context triple: [Niagara Centre, borderingCountryContext, near Canada–United States border]
-
A.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
B.
borderingCountryOfRegion
Indicates that a country shares a land or maritime border with a specified geographic region.
-
C.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9987cb0c8190af32a1193de54890 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.