Triple
T36501129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor-General of Min-Zhe |
E899330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Qing dynasty viceroyalty |
C33414
|
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: Qing dynasty viceroyalty Context triple: [Governor-General of Min-Zhe, instanceOf, Qing dynasty viceroyalty]
-
A.
Qing dynasty viceroy
chosen
A Qing dynasty viceroy was a high-ranking imperial official who governed one or more provinces, overseeing civil administration, military affairs, and tax collection on behalf of the emperor.
-
B.
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.
-
C.
Qing dynasty structure
A Qing dynasty structure is a building or architectural element constructed or styled during China’s Qing dynasty (1644–1912), typically featuring timber frameworks, bracket sets, sweeping roofs, and ornate decorative details reflecting imperial and regional aesthetics.
-
D.
Qing loyalist
A Qing loyalist is an individual who remains politically, culturally, or emotionally committed to the legitimacy and restoration of China’s Qing dynasty and its ruling ideals, often in opposition to republican or later regimes.
-
E.
Southern Ming regime
The Southern Ming regime was a series of short-lived, Ming loyalist courts that continued resistance against the Qing dynasty in southern China after the fall of Beijing in 1644.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.