Triple

T26023419
Position Surface form Disambiguated ID Type / Status
Subject The Tsar’s Bride E647215 entity
Predicate notableCharacter P1481 FINISHED
Object Grigory Gryaznoy
Grigory Gryaznoy is a central, dramatic figure in Nikolai Rimsky-Korsakov’s opera "The Tsar’s Bride," known for his intense jealousy and tragic role in the plot.
E1749679 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: Grigory Gryaznoy | Statement: [The Tsar’s Bride, notableCharacter, Grigory Gryaznoy]
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: Grigory Gryaznoy
Triple: [The Tsar’s Bride, notableCharacter, Grigory Gryaznoy]
Generated description
Grigory Gryaznoy is a central, dramatic figure in Nikolai Rimsky-Korsakov’s opera "The Tsar’s Bride," known for his intense jealousy and tragic role in the plot.

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_69e77e8b60e88190a3b26c4f0032a2c2 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f605e8c0a08190a34cad51a19e92de completed May 2, 2026, 2:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12296da1e081908a9d67ba72da0c80 completed May 23, 2026, 10:25 p.m.
NEDg Description generation batch_6a122a3a3b3c8190ab41feb5652546bb completed May 23, 2026, 10:29 p.m.
NED2 Entity disambiguation (via description) batch_6a122add10688190aa06ce1d690c1867 completed May 23, 2026, 10:31 p.m.
Created at: April 22, 2026, 9:05 a.m.