Triple

T3325810
Position Surface form Disambiguated ID Type / Status
Subject Division 2 E69911 entity
Predicate instanceOf P0 FINISHED
Object regulatory subdivision C13662 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: regulatory subdivision
Context triple: [Division 2, instanceOf, regulatory subdivision]
  • A. regional division
    A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
  • B. regional administrative branch
    A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
  • C. administrative territorial entity
    An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
  • D. overseas territory subdivision
    An overseas territory subdivision is an administrative division of a country located outside its mainland, typically subject to the sovereign state's authority while often possessing distinct legal, political, or cultural arrangements.
  • E. borough-level jurisdiction
    A borough-level jurisdiction is an administrative division within a larger city or region that possesses localized governmental authority and responsibilities specific to that borough.
  • F. None of above. chosen

Provenance (1 batch)

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_69ad85a1829881908942c14075644d0d completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:12 p.m.