Triple
T791252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan VI of Russia |
E16918
|
entity |
| Predicate | wasInfantRuler |
P16541
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ivan VI of Russia, wasInfantRuler, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInfantRuler Context triple: [Ivan VI of Russia, wasInfantRuler, true]
-
A.
cameToPowerAsMinor
chosen
Indicates that an individual assumed ruling authority or leadership while still legally or socially considered a minor.
-
B.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
-
C.
hasJuniorEmperorTitle
Indicates that an entity holds a subordinate or junior-level emperor title in relation to a higher-ranking imperial authority.
-
D.
ageAtStartOfReign
Indicates the age an individual was when they began their reign or rule.
-
E.
heirApparentDuringReign
Indicates that one entity was officially recognized as the designated heir apparent to another entity’s position or title during the latter’s period of reign.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79754988190ab494b1c54d6a2a4 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.