Triple

T33984934
Position Surface form Disambiguated ID Type / Status
Subject Azovsky District E871386 entity
Predicate hasSeparateAdministrativeUnit P36985 FINISHED
Object Azov NE NERFINISHED

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: Azov | Statement: [Azovsky District, hasSeparateAdministrativeUnit, Azov]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSeparateAdministrativeUnit
Context triple: [Azovsky District, hasSeparateAdministrativeUnit, Azov]
  • A. hasAdministrativeUnit
    Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
  • B. separatesAdministrativeUnits
    Indicates that one entity serves as a boundary or divider that distinguishes or splits different administrative units from each other.
  • C. hasSeparateUnit chosen
    Indicates that one entity exists or is treated as an independent, distinct unit from another entity.
  • D. establishedInAdministrativeUnit
    Indicates that something (such as an organization, facility, or institution) was founded or formally created within a specific administrative unit or jurisdiction.
  • E. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • 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_69f3499e964c8190b674b03f6f791b4b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff9b1ad27081908f8a492396950795 completed May 9, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69ff9a6354c48190ae21070c1424cb7a completed May 9, 2026, 8:34 p.m.
Created at: May 1, 2026, 1:50 a.m.