Triple
T34884734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | количество участников в группе D |
P101831
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [чемпионат мира по хоккею с шайбой 2008, количество участников в группе D, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: количество участников в группе D Context triple: [чемпионат мира по хоккею с шайбой 2008, количество участников в группе D, 4]
-
A.
numberOfTeamsGroupStage
Indicates the total count of teams that participate in the group stage of a competition or tournament.
-
B.
totalTeamsQualifyingFromGroup
Indicates the number of teams that advance from a particular group to the next stage of a competition.
-
C.
eliminatedTeamFromGroupD
Indicates that one entity caused another team to be removed from further competition in Group D.
-
D.
numberOfGroupMembers
Indicates the total count of individual members that belong to a specified group.
-
E.
teamsPerGroupInPreliminaryRound
chosen
Indicates how many teams are assigned to each group during the preliminary round of a competition or tournament.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4 p.m.