Triple
T13068925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Hockey League |
E329401
|
entity |
| Predicate | hasPlayoffChampion |
P22048
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Austrian Hockey League, hasPlayoffChampion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayoffChampion Context triple: [Austrian Hockey League, hasPlayoffChampion, true]
-
A.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
B.
playsChampionshipGame
Indicates that an entity participates as a competitor in a championship-level game or match.
-
C.
isAFCChampion
Indicates that an entity has won the championship title of the American Football Conference (AFC) in a given season.
-
D.
usedSinceForPlayoffConferenceChampion
Indicates that something (such as a rule, format, or criterion) has been in use since a certain time specifically for determining the playoff champion of a conference.
-
E.
playoffAchievement
chosen
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ec8ba48190baf52c7823482680 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.