Triple
T28187538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongshu Sheng |
E716218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial Chinese government institution |
C4989
|
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: imperial Chinese government institution Context triple: [Zhongshu Sheng, instanceOf, imperial Chinese government institution]
-
A.
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.
-
B.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
C.
institution of the Qing dynasty
An institution of the Qing dynasty is a formal political, administrative, military, social, or cultural organization or system established or sanctioned by the Qing imperial government to govern, regulate, and structure life within the empire.
-
D.
imperial official
An imperial official is a government functionary appointed by a sovereign empire to administer its laws, collect revenues, and enforce imperial authority within a designated jurisdiction.
-
E.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:23 p.m.