Triple
T26112205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Lock |
E658729
|
entity |
| Predicate | locatedOnSideOfBorder |
P67212
|
FINISHED |
| Object | Canadian side of Soo Locks |
—
|
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: Canadian side of Soo Locks | Statement: [Canadian Lock, locatedOnSideOfBorder, Canadian side of Soo Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfBorder Context triple: [Canadian Lock, locatedOnSideOfBorder, Canadian side of Soo Locks]
-
A.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
B.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
-
C.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
liesOnBorderOf
chosen
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 26, 2026, 8:02 p.m.