Triple
T34884717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | капитан чемпиона |
P19291
|
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.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
B.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
C.
losingCaptain
Indicates that the referenced captain is the one who lost in a particular contest, game, or competitive event.
-
D.
winForChampions
Indicates that the outcome of an event or competition results in a victory for the champions.
-
E.
winningCaptain
chosen
Indicates that the subject is the captain of a team that has won a particular match, tournament, or 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.