Triple
T6675533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concorde Bridge |
E151840
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Montreal |
E2604
|
NE 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: Montreal | Statement: [Concorde Bridge, connects, Montreal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Montreal Context triple: [Concorde Bridge, connects, Montreal]
-
A.
Montreal
chosen
Montreal is the largest city in Quebec, Canada, known for its vibrant bilingual culture, historic architecture, and status as a major economic and cultural center.
-
B.
Quebec City
Quebec City is the historic capital of the Canadian province of Quebec, renowned for its well-preserved fortified old town and rich French colonial heritage.
-
C.
Joliette
Joliette is a Montreal Metro station on the Green Line serving the Mercier–Hochelaga-Maisonneuve borough in Montreal, Quebec, Canada.
-
D.
Gatineau
Gatineau is a city in western Quebec, Canada, located across the Ottawa River from Ottawa and forming part of the National Capital Region.
-
E.
Trois-Rivières
Trois-Rivières is a historic industrial and cultural city in the Canadian province of Quebec, located roughly midway between Montreal and Quebec City.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b0f3021481908c2599349eb6ea07 |
completed | March 27, 2026, 4:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7813a788190a25ace732cf4e3d0 |
completed | March 27, 2026, 9:32 p.m. |
Created at: March 27, 2026, 2:03 p.m.