Triple
T12292775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Grigorievna Skuratova-Belskaya |
E293005
|
entity |
| Predicate | reignAsTsaritsaDuring |
P10353
|
FINISHED |
| Object | late 16th century |
—
|
LITERAL 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: late 16th century | Statement: [Maria Grigorievna Skuratova-Belskaya, reignAsTsaritsaDuring, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsTsaritsaDuring Context triple: [Maria Grigorievna Skuratova-Belskaya, reignAsTsaritsaDuring, late 16th century]
-
A.
successorAsTsaritsa
Indicates that one entity became the next Tsaritsa, directly succeeding another in that role.
-
B.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
C.
predecessorAsTsaritsa
Indicates that one entity previously held the position of tsaritsa immediately before the other entity.
-
D.
reignAsGrandDuchessConsortFrom
Indicates the time period during which a person held the role of grand duchess consort.
-
E.
eraAsEmpress
Indicates the time period during which a person held the role or status of empress.
- F. None of above.
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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d22ba488190914342fa7e69e159 |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c4ec6c4819085880bdefdd0f354 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.