Triple
T17851673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya |
E445820
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object | Ilya Kovalchuk |
—
|
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: Ilya Kovalchuk | Statement: [Ilya, hasNotableBearer, Ilya Kovalchuk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilya Kovalchuk Context triple: [Ilya, hasNotableBearer, Ilya Kovalchuk]
-
A.
Ilya Kovalchuk
chosen
Ilya Kovalchuk is a Russian former professional ice hockey winger known as one of the NHL’s elite goal scorers of the 2000s and early 2010s.
-
B.
Alexei Kovalchuk
Alexei Kovalchuk is a professional poker player known for his success in international tournaments and multiple major titles.
-
C.
Sergei Kovalchuk
Sergei Kovalchuk is a Belarusian football manager and former player known for his involvement in Eastern European club football.
-
D.
Vladimir Kovalchuk
Vladimir Kovalchuk is a person notable enough to be recognized as a bearer of the surname Kovalchuk.
-
E.
Yevgeni Kovalchuk
Yevgeni Kovalchuk is a Russian professional ice hockey player known for his career as a forward in domestic leagues.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48fff6c288190a2b5e60b66c03ddc |
completed | April 19, 2026, 8:19 a.m. |
Created at: April 10, 2026, 10:17 a.m.