Triple

T9482913
Position Surface form Disambiguated ID Type / Status
Subject Pronsky Uyezd E228687 entity
Predicate namedAfter P63 FINISHED
Object Pronsk E802535 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: Pronsk | Statement: [Pronsky Uyezd, namedAfter, Pronsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pronsk
Context triple: [Pronsky Uyezd, namedAfter, Pronsk]
  • A. Pronsk chosen
    Pronsk is a historic town in Ryazan Oblast, Russia, known for its medieval origins and role as a local administrative and cultural center.
  • B. Pestovo
    Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
  • C. Krasny Kut
    Krasny Kut is a small town in southwestern Russia known as an administrative and agricultural center within the Saratov region.
  • D. Andrusovo
    Andrusovo is a historic village in present-day Belarus known as the site where the 1667 Truce of Andrusovo between the Polish–Lithuanian Commonwealth and Tsardom of Russia was concluded.
  • E. Kraslava
    Kraslava is a small town in southeastern Latvia known for its historic architecture and scenic location near the borders with Belarus and Lithuania.
  • 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_69ca84730a5081908de282651019bf2f completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd804c859081908c261ad16b501f0d completed April 1, 2026, 8:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69d14bf604d4819092fc25f487866834 completed April 4, 2026, 5:35 p.m.
Created at: March 30, 2026, 7:55 p.m.