Triple
T16689319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yekaterina |
E405551
|
entity |
| Predicate | hasShortForm |
P43
|
FINISHED |
| Object | Katya |
E61396
|
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: Katya | Statement: [Yekaterina, hasShortForm, Katya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Katya Context triple: [Yekaterina, hasShortForm, Katya]
-
A.
Katya
chosen
Katya is a diminutive and affectionate form of the given name Catherine, commonly used in Slavic and other European cultures.
-
B.
Nadya
Nadya is a feminine given name, often used as a diminutive of Nadezhda in Slavic cultures.
-
C.
Nastya
Nastya is a tragic, idealistic young prostitute in Maxim Gorky’s play "The Lower Depths," known for her romantic fantasies and emotional vulnerability amid harsh social realities.
-
D.
Tatyana
Tatyana is a feminine given name of Slavic origin, particularly common in Russian-speaking countries.
-
E.
Ekaterina Maximova
Ekaterina Maximova was a celebrated Soviet and Russian ballerina renowned for her lyrical artistry and long-standing career as a principal dancer with the Bolshoi Ballet.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea80d88819091fc61ed3c01955a |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091966fbc81908cd1db230ddbb82b |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.