Triple
T30192502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanzhou |
E767530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Nine Provinces 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: traditional Nine Provinces region Context triple: [Yanzhou, instanceOf, traditional Nine Provinces 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.
region of Taiwan
A region of Taiwan is a geographically defined area within the island or its outlying territories, characterized by shared administrative, cultural, economic, or environmental features.
-
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.
subregion of Hunan
A subregion of Hunan is a geographically or administratively defined part of Hunan Province characterized by shared cultural, economic, or environmental features that distinguish it from other areas within the province.
-
E.
frontier province
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
- 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.