Triple
T12887254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feodosia Mikhailovna of Russia |
E308260
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object | Mikhailovna |
E998812
|
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: Mikhailovna | Statement: [Feodosia Mikhailovna of Russia, patronymic, Mikhailovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhailovna Context triple: [Feodosia Mikhailovna of Russia, patronymic, Mikhailovna]
-
A.
Mikhailovna
chosen
Mikhailovna is a Russian patronymic indicating descent from a father named Mikhail, commonly used as the middle name in female full names.
-
B.
Vasilyevna
Vasilyevna is a Russian female patronymic name indicating that the person's father is named Vasily.
-
C.
Kirillovna
Kirillovna is a Russian female patronymic indicating that the bearer is the daughter of someone named Kirill.
-
D.
Alekseyevna
Alekseyevna is a Russian patronymic surname suffix meaning "daughter of Alexei," historically borne by women such as Sophia Alekseyevna of Russia.
-
E.
Fyodorovna
Fyodorovna is a Russian patronymic name indicating that a woman is the daughter of someone named Fyodor.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714415c08190aa9944b494a3ddad |
completed | April 10, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a1a97748190992fe28c6411c4de |
completed | May 3, 2026, 8:40 a.m. |
Created at: April 9, 2026, 5:39 p.m.