Triple
T1274501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill University Library |
E15781
|
entity |
| Predicate | coordinatesRegion |
P16190
|
FINISHED |
| Object | downtown Montreal |
—
|
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: downtown Montreal | Statement: [McGill University Library, coordinatesRegion, downtown Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesRegion Context triple: [McGill University Library, coordinatesRegion, downtown Montreal]
-
A.
coordinateRegion
chosen
Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
-
B.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
D.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
E.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.