Triple

T34962680
Position Surface form Disambiguated ID Type / Status
Subject Могилёв-Подольский E1008301 entity
Predicate имеетИсторическуюЗастройку P295 FINISHED
Object центр города LITERAL 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: центр города | Statement: [Могилёв-Подольский, имеетИсторическуюЗастройку, центр города]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: имеетИсторическуюЗастройку
Context triple: [Могилёв-Подольский, имеетИсторическуюЗастройку, центр города]
  • A. residenceHistoric
    Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
  • B. isHistoricQuadrangleOf
    Indicates that one entity is a historically significant quadrangle (a four-sided courtyard or enclosed area) that belongs to, or is a defining part of, another entity such as a campus, complex, or site.
  • C. housingTypeHistoric
    Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
  • D. hasHistoricDistrict chosen
    Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
  • E. historicalStructure
    Indicates that the subject is a structure recognized for its historical significance or heritage value.
  • F. None of above.

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_69f76dc69564819099e9e78aed6ff0a6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7979a073881909a4fde2558e6b6f3 completed May 3, 2026, 6:44 p.m.
PD Predicate disambiguation batch_69f7961550f88190b7bb8a9155458b54 completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4 p.m.