Triple
T34681435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chunqiu Fanlu |
E890631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Han dynasty text |
C60114
|
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: Han dynasty text Context triple: [Chunqiu Fanlu, instanceOf, Han dynasty text]
-
A.
Song dynasty text
A Song dynasty text is a written work produced or compiled during China’s Song dynasty (960–1279), reflecting its era’s distinctive intellectual, literary, religious, and bureaucratic developments.
-
B.
Ming dynasty text
A Ming dynasty text is a written work produced in China between 1368 and 1644 that reflects the political, cultural, intellectual, or literary practices of the Ming period.
-
C.
Han dynasty commandery
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.
-
D.
Warring States–period manuscript
A Warring States–period manuscript is an ancient Chinese written document, typically inscribed on bamboo or silk between the 5th and 3rd centuries BCE, that preserves contemporary philosophical, political, legal, or literary texts from the era of competing states before imperial unification.
-
E.
Han dynasty princess
A Han dynasty princess is an imperial daughter or close female relative of the Han emperor, whose status, marriages, and political roles were used to secure alliances, consolidate power, and embody the prestige of the ruling house in ancient China.
- F. None of above. chosen
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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.