Triple
T33646487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Nagaya |
E861973
|
entity |
| Predicate | ordinalPositionAsWife |
P4764
|
FINISHED |
| Object | seventh wife of Ivan IV of Russia |
—
|
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: seventh wife of Ivan IV of Russia | Statement: [Maria Nagaya, ordinalPositionAsWife, seventh wife of Ivan IV of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalPositionAsWife Context triple: [Maria Nagaya, ordinalPositionAsWife, seventh wife of Ivan IV of Russia]
-
A.
marriedToRank
Indicates that one entity is married to another entity who holds a specific rank or position.
-
B.
positionOnMarriage
Indicates a person's stance, opinion, or policy regarding the institution or practice of marriage.
-
C.
motherSpouseOrder
Indicates that the subject is the spouse of the object’s mother, with an ordering or ranking among multiple such spouses.
-
D.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
E.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.