Triple
T7878600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002–03 AHL season |
E182919
|
entity |
| Predicate | championTitle |
P2682
|
FINISHED |
| Object | Calder Cup champion |
—
|
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: Calder Cup champion | Statement: [2002–03 AHL season, championTitle, Calder Cup champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championTitle Context triple: [2002–03 AHL season, championTitle, Calder Cup champion]
-
A.
championPreviousTitleYear
Indicates the year in which the current champion previously held the same title.
-
B.
championshipTitleWith
Indicates a relationship where two or more entities share or are jointly associated with the same championship title.
-
C.
championPreviousTitleSeason
Indicates that an entity was the champion of the immediately preceding season for a given title or competition.
-
D.
champion
chosen
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
E.
worldChampionTitleStart
Indicates the point in time when an entity first attains a world champion title in a given domain or competition.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bd64e481909f699e7dd2818b8f |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.