Triple
T12481910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irina Mikhailovna of Russia |
E298330
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Romanova |
E132184
|
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: Romanova | Statement: [Irina Mikhailovna of Russia, familyName, Romanova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romanova Context triple: [Irina Mikhailovna of Russia, 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.
Vladimira
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
-
C.
Pelageya
Pelageya is a Russian singer renowned for her powerful folk-inspired vocals and performances that blend traditional music with contemporary styles.
-
D.
Elisaveta
Elisaveta is a feminine given name of Slavic origin, commonly used in Eastern Europe as a variant of Elizabeth.
-
E.
Godunova
Godunova is the feminine form of the Russian surname Godunov, historically associated with the noble Godunov family of Russia.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dcef6548190a6d29375bdabd17d |
completed | April 10, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f29307c8190b024d889d45ba9f7 |
completed | May 2, 2026, 6:15 p.m. |
Created at: April 8, 2026, 9:56 p.m.