Triple

T9182425
Position Surface form Disambiguated ID Type / Status
Subject Smolninskoye Municipal Okrug E220364 entity
Predicate hasLocalSelfGovernment P86694 FINISHED
Object yes 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: yes | Statement: [Smolninskoye Municipal Okrug, hasLocalSelfGovernment, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalSelfGovernment
Context triple: [Smolninskoye Municipal Okrug, hasLocalSelfGovernment, yes]
  • A. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • B. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • C. hasLocalGovernmentOffice
    Indicates that a local government office is present or established within a specified location or jurisdiction.
  • D. hasLocalGovernmentCommunity
    Indicates that one entity possesses or is associated with a community-level local government authority responsible for administering that area.
  • E. hasLocalGovernmentJurisdictionOver
    Indicates that one governmental body possesses official authority to administer, regulate, and make binding decisions over a specific geographic area or population.
  • F. None of above. chosen

Provenance (4 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_69ca83e589948190ac9907819db11ddf completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccc2553e548190898434aeda517407 completed April 1, 2026, 6:59 a.m.
PD Predicate disambiguation batch_69cc66090e5881908889dc1213815626 completed April 1, 2026, 12:25 a.m.
PDg Predicate description generation batch_69cc66d7bf648190b8bff5b584b84975 completed April 1, 2026, 12:29 a.m.
Created at: March 30, 2026, 7:23 p.m.