Triple
T27992965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nongzheng Quanshu |
E706928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty text |
C53637
|
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: Ming dynasty text Context triple: [Nongzheng Quanshu, instanceOf, Ming dynasty text]
-
A.
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.
-
B.
Ming dynasty event
A Ming dynasty event is any historically significant occurrence—political, social, cultural, military, or economic—that took place during China’s Ming dynasty period (1368–1644).
-
C.
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.
-
D.
Ming dynasty person
A Ming dynasty person is an individual who lived under the rule of China’s Ming dynasty (1368–1644), participating in its social, political, economic, or cultural life.
-
E.
Ming dynasty government position
A Ming dynasty government position is an official role within the centralized imperial bureaucracy of the Ming dynasty, responsible for administering state affairs according to Confucian principles and imperial edicts.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:51 p.m.