Triple
T16487161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya Kabakov |
E400475
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ilya |
E445820
|
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: Ilya | Statement: [Ilya Kabakov, givenName, Ilya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilya Context triple: [Ilya Kabakov, givenName, Ilya]
-
A.
Ilya
chosen
Ilya is a common Russian given name, notably borne by star ice hockey player Ilya Kovalchuk.
-
B.
Yuri of Moscow
Yuri of Moscow was a 14th-century Grand Prince of Moscow and Vladimir who played a key role in the early rise of Muscovy through his political maneuvers and conflicts over the Vladimir-Suzdal throne.
-
C.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e078d0c8190a5698a5eb9df22d4 |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bafe159c8190b66d2cd21b8ddb88 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:13 a.m.