Triple
T13649469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya Kovalchuk |
E326691
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kovalchuk |
E326691
|
NE 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: Kovalchuk | Statement: [Ilya Kovalchuk, familyName, Kovalchuk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kovalchuk Context triple: [Ilya Kovalchuk, familyName, Kovalchuk]
-
A.
Kovalchuk
chosen
Kovalchuk is a common East Slavic surname, notably borne by several professional ice hockey players and other public figures from Russia, Ukraine, and Belarus.
-
B.
Kovalev
Kovalev is a common Russian surname borne by several notable figures in sports, politics, and the arts.
-
C.
Kovpak
Kovpak is a Ukrainian surname most notably associated with Sydir Kovpak, a famed Soviet partisan leader during World War II.
-
D.
Vasilevsky
Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
-
E.
Shevchuk
Shevchuk is a Ukrainian surname borne by numerous notable figures in fields such as religion, politics, sports, and the arts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc608466c81908f6d2c9c92cc86aa |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78afbf8948190ad38ea7529e52f16 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:52 p.m.