Triple
T27460527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor–Detroit border |
E692724
|
entity |
| Predicate | borderCityOnCanadianSide |
P155088
|
FINISHED |
| Object | Windsor, Ontario |
—
|
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: Windsor, Ontario | Statement: [Windsor–Detroit border, borderCityOnCanadianSide, Windsor, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCityOnCanadianSide Context triple: [Windsor–Detroit border, borderCityOnCanadianSide, Windsor, Ontario]
-
A.
hasBorderTownOnCanadianSide
chosen
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
-
B.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
-
C.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
D.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
-
E.
distanceToCanadianBorder
Indicates the measured or estimated spatial distance between a given location and the nearest point on the Canadian national 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 12:50 p.m.