Triple
T15161497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhaylovich |
E362226
|
entity |
| Predicate | distinguishedFrom |
P1612
|
FINISHED |
| Object | Mikhaylovna |
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: Mikhaylovna | Statement: [Mikhaylovich, distinguishedFrom, Mikhaylovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhaylovna Context triple: [Mikhaylovich, distinguishedFrom, Mikhaylovna]
-
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.
Maksimovna
Maksimovna is a Russian patronymic derived from the male given name Maksim, traditionally used as a middle name indicating "daughter of Maksim."
-
D.
Kirillovna
Kirillovna is a Russian female patronymic indicating that the bearer is the daughter of someone named Kirill.
-
E.
Yefimovna
Yefimovna is a Russian patronymic feminine middle name derived from the male given name Yefim.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060f2efc8190aa0eb5fb8d4ce085 |
completed | April 15, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec885d68c8190999529b69bc34fec |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:08 a.m.