Triple
T31695803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité du Multimédia |
E808913
|
entity |
| Predicate | cityMarketingRole |
P48445
|
FINISHED |
| Object | symbol of Montreal’s new economy |
—
|
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: symbol of Montreal’s new economy | Statement: [Cité du Multimédia, cityMarketingRole, symbol of Montreal’s new economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityMarketingRole Context triple: [Cité du Multimédia, cityMarketingRole, symbol of Montreal’s new economy]
-
A.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
cityPatron
Indicates that one entity serves as the patron, protector, or special guardian of a particular city.
-
C.
focusCityRole
Indicates that a city serves a particular primary role or function within a broader geographic or organizational context.
-
D.
cityPromotedAs
chosen
Indicates that a city is being advertised, marketed, or presented in a particular way or for a particular purpose.
-
E.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:10 p.m.