Triple

T26673494
Position Surface form Disambiguated ID Type / Status
Subject Leonov E672396 entity
Predicate hasNotableBearer P458 FINISHED
Object Nikolai Leonov
Nikolai Leonov was a high-ranking Soviet KGB intelligence officer and later a Russian politician known for his expertise on Latin America and involvement in state security affairs.
E1740289 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: Nikolai Leonov | Statement: [Leonov, hasNotableBearer, Nikolai Leonov]
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: Nikolai Leonov
Triple: [Leonov, hasNotableBearer, Nikolai Leonov]
Generated description
Nikolai Leonov was a high-ranking Soviet KGB intelligence officer and later a Russian politician known for his expertise on Latin America and involvement in state security affairs.

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_69eecda00a9c8190b2691f4d89db03b6 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6170129f88190a8d34212c7e030a4 completed May 2, 2026, 3:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12093120c88190ba81ddd0cadae2a4 completed May 23, 2026, 8:08 p.m.
NEDg Description generation batch_6a120a10905c819096fa77fad68b6bb8 completed May 23, 2026, 8:12 p.m.
NED2 Entity disambiguation (via description) batch_6a120aeed5ec819097f7ac08533bcf65 completed May 23, 2026, 8:15 p.m.
Created at: April 27, 2026, 3:14 a.m.