Triple
T32205049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | exo Laurentides |
E822645
|
entity |
| Predicate | transitArea |
P127691
|
FINISHED |
| Object | Greater Montreal |
—
|
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: Greater Montreal | Statement: [exo Laurentides, transitArea, Greater Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitArea Context triple: [exo Laurentides, transitArea, Greater Montreal]
-
A.
transitDistrict
Indicates that an entity is located within, governed by, or associated with a particular public transit administrative district.
-
B.
publicTransportArea
chosen
Indicates that a location or region is designated for or associated with public transportation services or facilities.
-
C.
publicTransportZone
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
-
D.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
E.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 12:36 a.m.