Triple
T26746283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasili the Blind |
E674410
|
entity |
| Predicate | successorAsGrandPrinceOfMoscow |
P94624
|
FINISHED |
| Object | Ivan III of Moscow |
—
|
NE NERFINISHED |
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: Ivan III of Moscow | Statement: [Vasili the Blind, successorAsGrandPrinceOfMoscow, Ivan III of Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsGrandPrinceOfMoscow Context triple: [Vasili the Blind, successorAsGrandPrinceOfMoscow, Ivan III of Moscow]
-
A.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
B.
successorAsTsaritsa
Indicates that one entity became the next Tsaritsa, directly succeeding another in that role.
-
C.
successorInRussia
chosen
Indicates that one entity is the direct successor of another in a Russian political, administrative, or institutional context.
-
D.
successorAsGrandDukeOfLithuania
Indicates that one entity became the next Grand Duke of Lithuania following another entity in succession.
-
E.
successorAsGrandDukeOfTuscany
Indicates the person who directly followed another as the Grand Duke of Tuscany in the line of succession.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 3:51 a.m.