Triple

T9149248
Position Surface form Disambiguated ID Type / Status
Subject Kashirsky Uyezd E219538 entity
Predicate hadLocalAdministration P61282 FINISHED
Object uyezd authorities 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: uyezd authorities | Statement: [Kashirsky Uyezd, hadLocalAdministration, uyezd authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadLocalAdministration
Context triple: [Kashirsky Uyezd, hadLocalAdministration, uyezd authorities]
  • A. hasOfficialAdministration
    Indicates that an entity is formally governed, managed, or overseen by an official administrative body or authority.
  • B. hasLocalGovernmentJurisdictionOver chosen
    Indicates that one governmental body possesses official authority to administer, regulate, and make binding decisions over a specific geographic area or population.
  • C. hasLocalGovernmentOffice
    Indicates that a local government office is present or established within a specified location or jurisdiction.
  • D. hasCountyAdministrativeBoard
    Indicates that an entity is under the jurisdiction or responsibility of a specific county administrative board.
  • E. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • 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_69ca83e121dc81909912bd66953081c5 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca96908d88190a1d12517f6d1aece completed April 1, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69cc6603ce8c8190bf6e8d6754bdec54 completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:20 p.m.