Triple
T21656255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Feodorovna |
E534474
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Romanova |
—
|
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: Romanova | Statement: [Maria Feodorovna, familyName, Romanova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romanova Context triple: [Maria Feodorovna, familyName, Romanova]
-
A.
Romanova
chosen
Romanova is the Russian feminine form of the dynastic surname Romanov, historically borne by female members of the imperial Romanov family.
-
B.
Maria Romanova
Maria Romanova is the mother of renowned Soviet ballerina Galina Ulanova.
-
C.
Vladlena Mishustina
Vladlena Mishustina is the wife of Russian Prime Minister Mikhail Mishustin and a public figure occasionally noted in Russian media for her role as his spouse.
-
D.
Vladimira
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
-
E.
Pelageya
Pelageya is a Russian singer renowned for her powerful folk-inspired vocals and performances that blend traditional music with contemporary styles.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59185b208190a2cf4b8f54a2c231 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 16, 2026, 6:36 p.m.