Triple
T34800634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Montreal |
E1003208
|
entity |
| Predicate | connectsCulturalCenter |
P125492
|
FINISHED |
| Object | 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: Montreal | Statement: [Toronto–Montreal, connectsCulturalCenter, Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCulturalCenter Context triple: [Toronto–Montreal, connectsCulturalCenter, Montreal]
-
A.
connectsCulturalHub
chosen
Indicates a relationship where one entity serves as a link or bridge to a central place or node of cultural activity, exchange, or significance.
-
B.
isCulturalCenterFor
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
-
C.
culturalOrganization
Indicates that an entity is an organization whose primary purpose involves cultural activities, preservation, or promotion.
-
D.
isCulturalCenter
Indicates that an entity serves as a primary hub or focal point for the cultural activities, expressions, and institutions of a community or region.
-
E.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 3:59 p.m.