Triple
T15725760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Emperor era (traditional) |
E381213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Chinese era |
C11193
|
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 Chinese era Context triple: [Yellow Emperor era (traditional), instanceOf, traditional Chinese era]
-
A.
era in Chinese history
chosen
An era in Chinese history is a distinct period marked by characteristic political structures, cultural developments, social changes, and significant events that differentiate it from other historical periods in China.
-
B.
Ming dynasty era
The Ming dynasty era was a period in Chinese history (1368–1644) marked by native Han rule, strong centralized bureaucracy, flourishing arts and literature, extensive maritime trade, and major architectural achievements such as the Forbidden City and sections of the Great Wall.
-
C.
Yuan dynasty era
The Yuan dynasty era refers to the period (1271–1368) when the Mongol-led Yuan dynasty ruled China, marked by vast Eurasian integration, cultural exchange, and significant developments in administration, trade, and the arts.
-
D.
Korean era name
A Korean era name is a specific title or phrase used to designate and number years during a monarch’s reign or a particular historical period in Korean history.
-
E.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.