Triple
T27916309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008–09 KHL season |
E706083
|
entity |
| Predicate | playoffsEnd |
P42827
|
FINISHED |
| Object | 2009-04-12 |
—
|
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: 2009-04-12 | Statement: [2008–09 KHL season, playoffsEnd, 2009-04-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffsEnd Context triple: [2008–09 KHL season, playoffsEnd, 2009-04-12]
-
A.
playoffsStartDate
Indicates the calendar date on which a competition’s playoff phase begins.
-
B.
postseasonEnd
chosen
Indicates the point in time or event at which a sports league’s postseason (playoffs) concludes.
-
C.
playoffsStatus
Indicates the current stage or outcome of an entity’s participation in a playoff competition (e.g., qualified, in progress, eliminated, or champion).
-
D.
playoffFinalsNumber
Indicates the specific number or sequence position of a playoff finals series or game within a playoff competition.
-
E.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:53 p.m.