Triple
T10409493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Nagaya |
E245349
|
entity |
| Predicate | afterIvanIVsDeath |
P93973
|
FINISHED |
| Object | sent with her son to Uglich |
—
|
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: sent with her son to Uglich | Statement: [Maria Nagaya, afterIvanIVsDeath, sent with her son to Uglich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterIvanIVsDeath Context triple: [Maria Nagaya, afterIvanIVsDeath, sent with her son to Uglich]
-
A.
successorAsTsaritsa
Indicates that one entity became the next Tsaritsa, directly succeeding another in that role.
-
B.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
C.
successorInVolhynia
Indicates that one entity directly followed another in holding authority or position in Volhynia.
-
D.
predecessorAsTsaritsa
Indicates that one entity previously held the position of tsaritsa immediately before the other entity.
-
E.
executedShortlyAfterDeathOf
Indicates that one entity was executed soon after the death of another entity, with only a short time interval separating the two events.
- F. None of above. chosen
Provenance (4 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9faa97c819092cadedadabe26bf |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:09 p.m.