Triple

T15562369
Position Surface form Disambiguated ID Type / Status
Subject Simbirsk fortress E371029 entity
Predicate locatedIn P40 FINISHED
Object Simbirsk E522034 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: Simbirsk | Statement: [Simbirsk fortress, locatedIn, Simbirsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Simbirsk
Context triple: [Simbirsk fortress, locatedIn, Simbirsk]
  • A. Simbirsk chosen
    Simbirsk is a historic Russian city on the Volga River, best known today as Ulyanovsk, the birthplace of Vladimir Lenin and other notable political figures.
  • B. Nizhny Novgorod
    Nizhny Novgorod is a major Russian city located at the confluence of the Volga and Oka rivers, known for its historic Kremlin, industrial significance, and role as a key cultural and economic center in the Volga region.
  • C. Izhevsk
    Izhevsk is a major industrial city in western Russia, best known as a center of arms manufacturing and the capital of the Udmurt Republic.
  • D. Sverdlovsk
    Sverdlovsk is the former name of Yekaterinburg, a major industrial and cultural city in Russia’s Ural region.
  • E. Penza
    Penza is a city in western Russia known as a regional cultural and industrial center.
  • 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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ddc66448190948280fb0c8d390c completed April 16, 2026, 2:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180bd1e5c8190a6a96581ce8a37de completed May 11, 2026, 7:09 a.m.
Created at: April 10, 2026, 4:09 a.m.