Triple
T11631812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilija |
E276415
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Ilija (Cyrillic: Илија) |
E276415
|
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: Ilija (Cyrillic: Илија) | Statement: [Ilija, hasVariantSpelling, Ilija (Cyrillic: Илија)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilija (Cyrillic: Илија) Context triple: [Ilija, hasVariantSpelling, Ilija (Cyrillic: Илија)]
-
A.
Ilija
chosen
Ilija is a masculine given name of Slavic origin, commonly used in countries such as Bulgaria, Serbia, and North Macedonia.
-
B.
Ilya
Ilya is a common Russian given name, notably borne by star ice hockey player Ilya Kovalchuk.
-
C.
Kirill
Kirill is a masculine given name of Slavic origin, commonly used in Russian-speaking and other Eastern European countries.
-
D.
Kirill
Kirill is a highly skilled Russian assassin and primary antagonist who relentlessly hunts Jason Bourne in the action thriller film "The Bourne Supremacy."
-
E.
Юрий (Cyrillic alphabet)
Юрий is the standard Cyrillic spelling of the Russian male given name equivalent to "Yuri" in English transliteration.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee87a20af481909b47775c7cb6ec3b |
completed | April 26, 2026, 9:46 p.m. |
Created at: April 8, 2026, 9:39 p.m.