Triple

T30543705
Position Surface form Disambiguated ID Type / Status
Subject Dankov E777351 entity
Predicate formerAdministrativeUnitType P198575 FINISHED
Object uyezd center 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 center | Statement: [Dankov, formerAdministrativeUnitType, uyezd center]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerAdministrativeUnitType
Context triple: [Dankov, formerAdministrativeUnitType, uyezd center]
  • A. administrativeUnitType
    Indicates the specific kind or category of administrative unit involved in the relationship (e.g., city, county, province).
  • B. laterAdministrativeUnit
    Indicates that one administrative unit succeeds or replaces another in time, coming into effect at a later date.
  • C. previousAdministrativeUnit
    Indicates that one administrative unit was the immediate predecessor or former governing unit of another in an administrative hierarchy or history.
  • D. successorAdministrativeUnit
    Indicates that one administrative unit has officially replaced another in its governing or jurisdictional role.
  • E. isAdministrativeUnit
    Indicates that one entity functions as an official administrative division or unit within the governance or organizational structure of another entity.
  • 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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fef3ceef648190b58027c93d757438 completed May 9, 2026, 8:43 a.m.
PD Predicate disambiguation batch_69fef359da2c819091a034387b08821f completed May 9, 2026, 8:42 a.m.
PDg Predicate description generation batch_69fef3cdea708190af41c1ff23b68f88 completed May 9, 2026, 8:43 a.m.
Created at: April 29, 2026, 8:19 p.m.