Triple

T3931519
Position Surface form Disambiguated ID Type / Status
Subject Yanqing District E90803 entity
Predicate instanceOf P0 FINISHED
Object administrative territorial entity of China C740 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: administrative territorial entity of China
Context triple: [Yanqing District, instanceOf, administrative territorial entity of China]
  • A. administrative territorial entity chosen
    An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
  • B. autonomous region of China
    An autonomous region of China is a first-level administrative division granted a degree of self-governance and cultural autonomy, typically in areas with significant ethnic minority populations.
  • C. Special Administrative Region of China
    A Special Administrative Region of China is a highly autonomous territorial unit under Chinese sovereignty that maintains its own legal, economic, and administrative systems distinct from those of mainland China.
  • D. former administrative territorial entity
    A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
  • E. autonomous prefecture
    An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
  • F. None of above.

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_69aed95f26e0819094b0e71974543a19 completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:23 p.m.