Triple
T34884738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | следующий турнир |
P69447
|
FINISHED |
| Object | чемпионат мира по хоккею с шайбой 2009 |
—
|
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: чемпионат мира по хоккею с шайбой 2009 | Statement: [чемпионат мира по хоккею с шайбой 2008, следующий турнир, чемпионат мира по хоккею с шайбой 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: следующий турнир Context triple: [чемпионат мира по хоккею с шайбой 2008, следующий турнир, чемпионат мира по хоккею с шайбой 2009]
-
A.
nextTournament
chosen
Indicates that one entity is the immediately upcoming tournament scheduled to occur for the other entity.
-
B.
nextRound
Indicates that one event, state, or step directly follows another in the subsequent round or iteration.
-
C.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
D.
followedByTournament
Indicates that one event or period is immediately succeeded by a tournament.
-
E.
laterCompetitionName
Indicates that an entity has its name changed to a different one in a subsequent or later 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.