Triple

T13952125
Position Surface form Disambiguated ID Type / Status
Subject Nevelsky District E335551 entity
Predicate hasMunicipalFormationType P33889 FINISHED
Object municipal district 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: municipal district | Statement: [Nevelsky District, hasMunicipalFormationType, municipal district]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMunicipalFormationType
Context triple: [Nevelsky District, hasMunicipalFormationType, municipal district]
  • A. hasMunicipalityType
    Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
  • B. hasMunicipalFormation chosen
    Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
  • C. isPartOfMunicipalityType
    Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
  • D. hasCityGovernmentType
    Indicates the specific form or structure of municipal governance that administers a city.
  • E. hasMunicipalAgencyType
    Indicates that a municipal agency is classified as having a specific organizational or functional type.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e146720819085d0f5eae558b7a4 completed April 14, 2026, 12:07 p.m.
PD Predicate disambiguation batch_69de05a3ccf88190b45c742db483fa08 completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:17 p.m.