Triple
T29363159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHL Kelly Cup Playoffs |
E744645
|
entity |
| Predicate | determinesChampionOf |
P29352
|
FINISHED |
| Object | ECHL |
—
|
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: ECHL | Statement: [ECHL Kelly Cup Playoffs, determinesChampionOf, ECHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinesChampionOf Context triple: [ECHL Kelly Cup Playoffs, determinesChampionOf, ECHL]
-
A.
determinesChampionBy
chosen
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
B.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
C.
determinedPennantWinnerFor
Indicates that one entity has been determined as the pennant-winning team for a particular league, season, or competition.
-
D.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
E.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669894f608190941fed17608d9c2e |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:20 p.m.