Triple

T30809541
Position Surface form Disambiguated ID Type / Status
Subject Vsevolod of Yuriev-Polsky E784605 entity
Predicate positionHeld P8 FINISHED
Object prince of Yuriev-Polsky
The prince of Yuriev-Polsky was a medieval Rus’ ruler who governed the small principality centered on the town of Yuriev-Polsky in northeastern Rus’.
E1933822 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: prince of Yuriev-Polsky | Statement: [Vsevolod of Yuriev-Polsky, positionHeld, prince of Yuriev-Polsky]
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: prince of Yuriev-Polsky
Triple: [Vsevolod of Yuriev-Polsky, positionHeld, prince of Yuriev-Polsky]
Generated description
The prince of Yuriev-Polsky was a medieval Rus’ ruler who governed the small principality centered on the town of Yuriev-Polsky in northeastern Rus’.

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_69f224b3a7ec819096939414d103e31e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6904138088190ad4209ce7caa4ea3 completed May 3, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28bbdddd6081908e699bf4476615db completed June 10, 2026, 1:20 a.m.
NEDg Description generation batch_6a28bda7d45881909ac66e31b6a9e81c completed June 10, 2026, 1:28 a.m.
NED2 Entity disambiguation (via description) batch_6a28beb8708081909929053567fe8249 completed June 10, 2026, 1:32 a.m.
Created at: April 29, 2026, 8:43 p.m.