Triple
T34884723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | лучший бомбардир |
P6605
|
FINISHED |
| Object | Дэнни Хитли |
—
|
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: Дэнни Хитли | Statement: [чемпионат мира по хоккею с шайбой 2008, лучший бомбардир, Дэнни Хитли]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: лучший бомбардир Context triple: [чемпионат мира по хоккею с шайбой 2008, лучший бомбардир, Дэнни Хитли]
-
A.
fastestGoalScorer
Indicates that the subject is the player who scored a goal in the shortest time (e.g., from match start or appearance) compared to others.
-
B.
topScorer
chosen
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
C.
mostPointsPerGamePlayer
Indicates the player who has the highest average number of points scored per game within a given context or season.
-
D.
notableGoalScorer
Indicates that the subject is recognized for having scored a significant or noteworthy number of goals, typically in a sports context.
-
E.
goalScorer
Indicates that the subject is the player who scored a particular goal in a game or match.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.