Triple
T6812558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mykola |
E156670
|
entity |
| Predicate | shortFormPossible |
P25216
|
FINISHED |
| Object | Kolya |
E446528
|
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: Kolya | Statement: [Mykola, shortFormPossible, Kolya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kolya Context triple: [Mykola, shortFormPossible, Kolya]
-
A.
Kolya
chosen
Kolya is a charismatic, roguish young Russian soldier in David Benioff’s novel "City of Thieves," known for his wit, bravado, and unlikely friendship with the protagonist during the Siege of Leningrad.
-
B.
Olyusha
Olyusha is a Russian diminutive form of the female given name Olga, typically used as an affectionate nickname.
-
C.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
D.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d329861881909f65bd1017ea384b |
completed | March 27, 2026, 6:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7425a26d88190ab1e3de2e5596108 |
completed | March 28, 2026, 2:52 a.m. |
Created at: March 27, 2026, 2:17 p.m.