Triple
T16874842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalia Staritskaya |
E421271
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Natalia |
E281523
|
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: Natalia | Statement: [Natalia Staritskaya, givenName, Natalia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Natalia Context triple: [Natalia Staritskaya, givenName, Natalia]
-
A.
Natalia
Natalia was a short-lived Boer republic established in the 1830s in what is now KwaZulu-Natal, South Africa.
-
B.
Natalya
chosen
Natalya is a feminine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Latin name Natalia.
-
C.
Nadya
Nadya is a feminine given name, often used as a diminutive of Nadezhda in Slavic cultures.
-
D.
Ksenia
Ksenia is a feminine given name, commonly used in Slavic countries and derived from the Greek name Xenia, meaning "hospitality" or "guest-friendship."
-
E.
Yelena
Yelena is a feminine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Helen or Helena in English.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f5290481909e0fd0af30935fcd |
completed | April 18, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2b2e67c81908e2313491d16353f |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:29 a.m.