Triple

T34533097
Position Surface form Disambiguated ID Type / Status
Subject Markov E886592 entity
Predicate hasNotableBearer P458 FINISHED
Object Yuri Markov
Yuri Markov is a personal name shared by multiple individuals, most commonly associated with Russian or Eastern European figures in fields such as sports, academia, or the arts.
E2294041 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: Yuri Markov | Statement: [Markov, hasNotableBearer, Yuri Markov]
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: Yuri Markov
Triple: [Markov, hasNotableBearer, Yuri Markov]
Generated description
Yuri Markov is a personal name shared by multiple individuals, most commonly associated with Russian or Eastern European figures in fields such as sports, academia, or the arts.

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_69f349cd7c148190aa99192b126d1527 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71fe94f74819083b4598e21e19871 completed May 3, 2026, 10:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7b693799fc8190978be8a67e8e389b completed Aug. 11, 2026, 6:25 p.m.
NEDg Description generation batch_6a7b6aa632d881908e30a5d036503653 completed Aug. 11, 2026, 6:32 p.m.
NED2 Entity disambiguation (via description) batch_6a7b6c2575bc81909d40c5eb8aecd7d9 completed Aug. 11, 2026, 6:38 p.m.
Created at: May 1, 2026, 2:02 a.m.