Triple

T30192500
Position Surface form Disambiguated ID Type / Status
Subject Yanzhou E767530 entity
Predicate instanceOf P0 FINISHED
Object ancient Chinese region C35417 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: ancient Chinese region
Context triple: [Yanzhou, instanceOf, ancient Chinese region]
  • A. historical province of China chosen
    A historical province of China is a former administrative region that once functioned as a distinct territorial unit under Chinese dynastic or early modern governments but has since been reorganized, renamed, or dissolved in later administrative reforms.
  • B. ancient Chinese state
    An ancient Chinese state is a historically documented political entity that existed within the territory of what is now China, characterized by its own ruling house, administrative system, culture, and military, and interacting with neighboring states through warfare, diplomacy, and trade.
  • C. 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.
  • D. plain of China
    The plain of China is a vast, low-lying expanse of fertile land, primarily in eastern China, that supports dense populations and intensive agriculture.
  • E. ancient Chinese city
    An ancient Chinese city is a fortified urban center that served as a political, economic, military, and cultural hub, characterized by planned layouts, defensive walls, gates, palaces, temples, markets, and residential quarters reflecting traditional Chinese cosmology and social hierarchy.
  • 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_69f2247db1108190835c0727c97637c3 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:29 p.m.