Triple

T23392512
Position Surface form Disambiguated ID Type / Status
Subject Volozhin E594055 entity
Predicate administrativeCenterOf P383 FINISHED
Object Volozhin District 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: Volozhin District | Statement: [Volozhin, administrativeCenterOf, Volozhin District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volozhin District
Context triple: [Volozhin, administrativeCenterOf, Volozhin District]
  • A. Volozhin District chosen
    Volozhin District is an administrative district in the Minsk Region of Belarus, centered around the town of Volozhin.
  • B. Gomelsky District
    Gomelsky District is an administrative district centered around the city of Gomel in southeastern Belarus.
  • C. Porkhovsky District
    Porkhovsky District is an administrative district in Pskov Oblast, Russia, known for its rural settlements and historical towns in the western part of the country.
  • D. Dzyarzhynsk District
    Dzyarzhynsk District is an administrative district in Belarus known for containing Dzyarzhynskaya Hara, the country’s highest point.
  • E. Lyuberetsky District
    Lyuberetsky District is an administrative and municipal district in Moscow Oblast, Russia, located southeast of Moscow and centered around the city of Lyubertsy.
  • 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a49df4308190ab4ab31310af81ed completed April 29, 2026, 6:26 a.m.
Created at: April 17, 2026, 5:36 p.m.