Triple
T3592370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margarita Petrovna |
E76054
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object | Petrovna |
E295292
|
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: Petrovna | Statement: [Margarita Petrovna, patronymic, Petrovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrovna Context triple: [Margarita Petrovna, patronymic, Petrovna]
-
A.
Petrovna
chosen
Petrovna is a common Russian patronymic derived from the male given name Pyotr, typically meaning "daughter of Pyotr."
-
B.
Pavlovna
Pavlovna is a Russian patronymic indicating "daughter of Pavel," commonly used as the middle name of women in Russian naming tradition.
-
C.
Nikolaevna
Nikolaevna is a Russian patronymic indicating "daughter of Nikolai," famously borne by Grand Duchess Anastasia Nikolaevna of Russia.
-
D.
Martha Apraksina
Martha Apraksina was a Russian noblewoman best known as the second wife of Tsar Feodor III of Russia.
-
E.
Natalia Petrovna
Natalia Petrovna was a Russian princess of the Romanov dynasty and sister of Empress Elizabeth 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4030bc5f081908d56edc4ff550d77 |
completed | March 13, 2026, 12:28 p.m. |
Created at: March 8, 2026, 3:22 p.m.