Triple

T16137265
Position Surface form Disambiguated ID Type / Status
Subject Ivan II of Moscow E391562 entity
Predicate historicalRegion P915 FINISHED
Object Rusʼ E158473 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: Rusʼ | Statement: [Ivan II of Moscow, historicalRegion, Rusʼ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rusʼ
Context triple: [Ivan II of Moscow, 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. Rusa
    Rusa is a genus of deer native to South and Southeast Asia, including species such as the Javan rusa and sambar.
  • E. Russas
    Russas is a municipality in the northeastern Brazilian state of Ceará, known for its agricultural activities and semi-arid climate.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a05e68881908319454a478cdda5 completed April 17, 2026, 11:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff7a304348190bf471f2b9279b806 completed May 10, 2026, 3:12 a.m.
Created at: April 10, 2026, 5:01 a.m.