Triple

T2246858
Position Surface form Disambiguated ID Type / Status
Subject Vasili IV Shuisky E49523 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: [Vasili IV Shuisky, familyName, Shuisky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shuisky
Context triple: [Vasili IV 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. Kastornoye
    Kastornoye is a locality in Russia historically notable as the namesake and focal area of the Voronezh–Kastornoye military offensive during World War II.
  • C. Vyatskoye
    Vyatskoye is a rural locality in Russia’s Khabarovsk Krai, historically noted as the birthplace of North Korean leader Kim Jong Il.
  • D. Shakhovskoye
    Shakhovskoye is a rural locality in Russia known primarily as the birthplace of Soviet politician Mikhail Suslov.
  • E. Borovitskaya
    Borovitskaya is a Moscow Metro station located in the city center, providing key interchange access between several central lines.
  • 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_69a88aa979788190ad6500f1d8eee2fc completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc0ec46b08190ae12de8b255eb71d completed March 7, 2026, 6:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69b0559265388190b070de8b92c6e95b completed March 10, 2026, 5:32 p.m.
Created at: March 4, 2026, 7:47 p.m.