Triple
T17418746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President's Cup (WHL) |
E423552
|
entity |
| Predicate | trophyOf |
P2890
|
FINISHED |
| Object | Western Hockey League playoffs |
—
|
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: Western Hockey League playoffs | Statement: [President's Cup (WHL), trophyOf, Western Hockey League playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyOf Context triple: [President's Cup (WHL), trophyOf, Western Hockey League playoffs]
-
A.
trophy
chosen
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
B.
trophyUse
Indicates that an entity uses, employs, or utilizes a trophy in some manner or context.
-
C.
trophyNameRefersTo
Indicates that a given trophy name refers to, denotes, or is associated with a particular trophy entity.
-
D.
trophyCustodian
Indicates that one entity is responsible for holding, safeguarding, or managing a trophy on behalf of another entity or organization.
-
E.
trophyWonWith
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44234d840819096484a15d407785a |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.