Triple

T21320176
Position Surface form Disambiguated ID Type / Status
Subject Yuri Dmitrievich of Zvenigorod E525589 entity
Predicate historicalRegion P915 FINISHED
Object Rus' NE NERFINISHED

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: Rus' | Statement: [Yuri Dmitrievich of Zvenigorod, historicalRegion, Rus']
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rus'
Context triple: [Yuri Dmitrievich of Zvenigorod, historicalRegion, Rus']
  • A. Rus' chosen
    Rus' was a medieval East Slavic state that emerged in Eastern Europe and laid the foundations for the later Russian, Ukrainian, and Belarusian nations.
  • B. Rusko
    Rusko is a small municipality in southwestern Finland known for its rural character and proximity to the city of Turku.
  • C. Rusko
    Rusko is a British electronic music producer and DJ known for pioneering the modern dubstep sound.
  • D. Rusguniae
    Rusguniae was an important ancient coastal city in the Roman province of Mauretania Caesariensis, located in what is now northern Algeria.
  • E. Rusa
    Rusa is a genus of deer native to South and Southeast Asia, including species such as the Javan rusa and sambar.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ed0a2788190b6a71c8c720173dc completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:39 p.m.