Triple

T30361889
Position Surface form Disambiguated ID Type / Status
Subject Oleg Ivanovich of Ryazan E772309 entity
Predicate successor P78 FINISHED
Object Fyodor Olegovich of Ryazan
Fyodor Olegovich of Ryazan was a medieval Rus’ prince who ruled the Principality of Ryazan following the reign of his father, Oleg Ivanovich.
E772309 NE 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: Fyodor Olegovich of Ryazan | Statement: [Oleg Ivanovich of Ryazan, successor, Fyodor Olegovich of Ryazan]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fyodor Olegovich of Ryazan
Triple: [Oleg Ivanovich of Ryazan, successor, Fyodor Olegovich of Ryazan]
Generated description
Fyodor Olegovich of Ryazan was a medieval Rus’ prince who ruled the Principality of Ryazan following the reign of his father, Oleg Ivanovich.

Provenance (5 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_69f2248c6f5c8190a6177842bf791a3c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68243b5d8819092d8a0a1261f5fb2 completed May 2, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2a71e68b58819092220cea6567f724 completed June 11, 2026, 8:29 a.m.
NEDg Description generation batch_6a2a750a34d08190a0c9ee938c828b44 completed June 11, 2026, 8:42 a.m.
NED2 Entity disambiguation (via description) batch_6a2a8e22cf9081909b2af52238c04431 completed June 11, 2026, 10:29 a.m.
Created at: April 29, 2026, 7:58 p.m.