Triple
T16992710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montréal en Lumière |
E412232
|
entity |
| Predicate | organisedInSeason |
P91622
|
FINISHED |
| Object | winter |
—
|
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: winter | Statement: [Montréal en Lumière, organisedInSeason, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organisedInSeason Context triple: [Montréal en Lumière, organisedInSeason, winter]
-
A.
organisedIn
Indicates that an event, activity, or entity is arranged, coordinated, or held within a particular place, context, or organizational framework.
-
B.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
C.
playsInSeasonStructure
Indicates that an entity (such as a team or player) participates in or is scheduled to compete within a particular season structure or competition format.
-
D.
organisedInMonth
Indicates that an event or activity was arranged or took place during a specific calendar month.
-
E.
hostedInSeason
chosen
Indicates that an event, show, or activity took place or was held during a specific season.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d283d2388190a78bf8d179e83fdc |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.