Triple
T36791465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Cup |
E909063
|
entity |
| Predicate | awardedInLeague |
P24781
|
FINISHED |
| Object | United Hockey League |
—
|
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: United Hockey League | Statement: [Colonial Cup, awardedInLeague, United Hockey League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedInLeague Context triple: [Colonial Cup, awardedInLeague, United Hockey League]
-
A.
awardedToLeagueMember
Indicates that something (such as an award, honor, or recognition) is given to a member of a specific league.
-
B.
wonLeagueWith
Indicates that an entity achieved victory in a league competition while being a member of or associated with another entity (such as a team or club).
-
C.
leagueOfAward
chosen
Indicates that an award is associated with, given within, or governed by a particular league or organized competition.
-
D.
isTopIndividualHonorInLeague
Indicates that an honor represents the highest individual award given within a particular league.
-
E.
wasInitiallySingleLeagueAward
Indicates that an award was originally given within a single unified league before any later league splits or structural changes.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:12 p.m.