Triple
T33881446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999–2000 QMJHL season |
E868500
|
entity |
| Predicate | executiveOfTheYearAward |
P50409
|
FINISHED |
| Object | John Horman Trophy |
—
|
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: John Horman Trophy | Statement: [1999–2000 QMJHL season, executiveOfTheYearAward, John Horman Trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executiveOfTheYearAward Context triple: [1999–2000 QMJHL season, executiveOfTheYearAward, John Horman Trophy]
-
A.
awardForYear
Indicates that an award is associated with, or was given in, a specific year.
-
B.
managerialAward
chosen
Indicates that an entity receives or is granted an award specifically recognizing managerial performance, responsibilities, or achievements in a management role.
-
C.
workAwardYear
Indicates the year in which a particular work received a specific award.
-
D.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
-
E.
permanentAwardYear
Indicates the specific year in which a permanent award or honor was formally granted or established.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.