Triple
T34595969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre Georges-Vézina |
E888308
|
entity |
| Predicate | namedForTeamOfEponym |
P38171
|
FINISHED |
| Object | Montreal Canadiens |
—
|
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 Canadiens | Statement: [Centre Georges-Vézina, namedForTeamOfEponym, Montreal Canadiens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForTeamOfEponym Context triple: [Centre Georges-Vézina, namedForTeamOfEponym, Montreal Canadiens]
-
A.
namedForTeam
chosen
Indicates that one entity has been given its name in honor of, or derived from, a particular team.
-
B.
eponymPlayedFor
Indicates that the eponymous person or entity was a member of, or played for, a particular team or organization.
-
C.
teamKnownFor
Indicates that a team is widely recognized or notable for a particular characteristic, achievement, activity, or attribute.
-
D.
eponymKnownFor
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
E.
namedForNationality
Indicates that something is named after or in reference to a particular nationality or national identity.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 2:03 a.m.