Triple

T11314359
Position Surface form Disambiguated ID Type / Status
Subject Ivan Andreyevich Shuisky E267925 entity
Predicate familyName P18 FINISHED
Object Shuisky E259608 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: Shuisky | Statement: [Ivan Andreyevich Shuisky, familyName, Shuisky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shuisky
Context triple: [Ivan Andreyevich Shuisky, familyName, Shuisky]
  • A. Shuisky chosen
    Shuisky is a scheming boyar and political intriguer in Alexander Pushkin’s historical drama and Modest Mussorgsky’s opera "Boris Godunov."
  • B. Yukhnov
    Yukhnov is a small historic town in western Russia known for its location on the Ugra River and its role in regional trade and World War II history.
  • C. Yuzovka
    Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
  • D. Nikolskoye
    Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
  • E. Nikolskoye
    Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9c2c7b081909af8acebc8aa93aa completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e50a910a2c8190b8afd4c988e64141 completed April 19, 2026, 5:02 p.m.
Created at: April 8, 2026, 9:32 p.m.