Triple

T31496996
Position Surface form Disambiguated ID Type / Status
Subject Guangling E803571 entity
Predicate instanceOf P0 FINISHED
Object historical commandery C41794 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: historical commandery
Context triple: [Guangling, instanceOf, historical commandery]
  • A. Han dynasty commandery chosen
    A Han dynasty commandery was an administrative division governed by a centrally appointed commandery governor, responsible for civil administration, tax collection, and local security within a defined territorial region of the Han Empire.
  • B. historic city-state
    A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
  • C. 歴史都市
    歴史都市とは、長い歴史の中で形成された都市構造・建築・文化・生活様式などが現在も色濃く残り、その歴史的価値が都市のアイデンティティや景観を特徴づけている都市である。
  • D. 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.
  • E. prefectural-level city (historical)
    A prefectural-level city (historical) is an administrative division that historically combined an urban center with its surrounding rural areas under a single prefecture-level government, often serving as a regional political, economic, and cultural hub.
  • 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_69f348cae52081909fa8e5f697523ae3 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 9:41 p.m.