Triple
T16689313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yekaterina |
E405551
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Ekaterina |
—
|
NE NERFINISHED |
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: Ekaterina | Statement: [Yekaterina, hasVariant, Ekaterina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ekaterina Context triple: [Yekaterina, hasVariant, Ekaterina]
-
A.
Yekaterina
chosen
Yekaterina is a common Russian female given name, equivalent to Catherine in English.
-
B.
Anna Karlovna
Anna Karlovna is an alternative name for Anna Leopoldovna, the 18th-century Russian regent who ruled on behalf of the infant Emperor Ivan VI.
-
C.
Tsesarevna of Russia
Tsesarevna of Russia was the title traditionally borne by the daughters or female-line heirs of a Russian tsar, denoting their status as imperial princesses in the Russian monarchy.
-
D.
Elisaveta
Elisaveta is a feminine given name of Slavic origin, commonly used in Eastern Europe as a variant of Elizabeth.
-
E.
Natalia Petrovna of Russia
Natalia Petrovna of Russia was a Russian noblewoman of the imperial era, known as a member of the extended Romanov family.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 5:19 a.m.