Triple
T36614466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USHL Eastern Conference |
E903564
|
entity |
| Predicate | hasChampionOutcome |
P33358
|
FINISHED |
| Object | conference champion competes for Clark Cup |
—
|
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: conference champion competes for Clark Cup | Statement: [USHL Eastern Conference, hasChampionOutcome, conference champion competes for Clark Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionOutcome Context triple: [USHL Eastern Conference, hasChampionOutcome, conference champion competes for Clark Cup]
-
A.
championWins
Indicates that a champion emerges victorious in a competition, match, or contest.
-
B.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
C.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
D.
hadChampionTeam
Indicates that an entity (such as a league, season, or competition) had a specific team recognized as its champion.
-
E.
subsequentChampionshipResult
Indicates the outcome or result of a championship that occurs immediately after a referenced earlier championship.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:11 p.m.