Triple
T26157358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sault Ste. Marie Bridge Authority |
E660000
|
entity |
| Predicate | bridgeConnectsCountry |
P99274
|
FINISHED |
| Object | Canada |
—
|
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: Canada | Statement: [Sault Ste. Marie Bridge Authority, bridgeConnectsCountry, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeConnectsCountry Context triple: [Sault Ste. Marie Bridge Authority, bridgeConnectsCountry, Canada]
-
A.
connectsCountryBorder
Indicates that one entity forms a direct land or maritime border connection with a specified country.
-
B.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
-
C.
connectsStates
Indicates a relationship where one entity serves as a link or route that joins two or more states together.
-
D.
borderingCountryConnectivity
Indicates that two countries share a land or maritime border that allows direct movement or interaction between them.
-
E.
connectsCountryOrRegion
chosen
Indicates that one entity establishes a connection, link, or association to a specific country or region.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c10f82c8190a102d95ec1941efc |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:28 p.m.