Triple
T20752355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anastasia |
E510756
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Anastasiya |
—
|
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: Anastasiya | Statement: [Anastasia, hasVariant, Anastasiya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anastasiya Context triple: [Anastasia, hasVariant, Anastasiya]
-
A.
Nadya
Nadya is a feminine given name, often used as a diminutive of Nadezhda in Slavic cultures.
-
B.
Stasya
chosen
Stasya is a diminutive or affectionate Russian nickname commonly used for the female given name Anastasia.
-
C.
Evgenia
Evgenia is a feminine given name commonly used in Slavic and Greek cultures, derived from the Greek name Eugenia meaning "well-born" or "noble."
-
D.
Anastazy
Anastazy is a masculine given name of Polish origin, historically borne by several notable figures including nobles and clergy.
-
E.
Natalya
Natalya is a feminine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Latin name Natalia.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22be6588190b137193cb3184fc0 |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:34 p.m.