Triple

T13827758
Position Surface form Disambiguated ID Type / Status
Subject Konakovo E332297 entity
Predicate isPartOf P10 FINISHED
Object Konakovsky District E1212529 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: Konakovsky District | Statement: [Konakovo, isPartOf, Konakovsky District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konakovsky District
Context triple: [Konakovo, isPartOf, Konakovsky District]
  • A. Konakovsky District chosen
    Konakovsky District is an administrative district (raion) of Tver Oblast in Russia, located along the Volga River and centered on the town of Konakovo.
  • B. Chaunsky District
    Chaunsky District is an administrative district in Russia’s Chukotka Autonomous Okrug, known for encompassing the Arctic port town of Pevek.
  • C. Kimrsky District
    Kimrsky District is an administrative district in Tver Oblast, Russia, centered around the town of Kimry and encompassing the surrounding rural areas.
  • D. Chudovsky District
    Chudovsky District is an administrative and municipal district in Novgorod Oblast, Russia, centered around the town of Chudovo.
  • E. Engelsky District
    Engelsky District is an administrative district in Saratov Oblast, Russia, centered around the city of Engels on the Volga River.
  • 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_69d81c5ae7c88190b0dd41bdafeb5999 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0295d2d48190b08eba0d805bd72d completed April 14, 2026, 9:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004568c93c81908450887f72de8466 completed May 10, 2026, 8:44 a.m.
Created at: April 9, 2026, 10:13 p.m.