Triple
T33600898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan family of Shanghai |
E860717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty lineage |
C18227
|
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 lineage Context triple: [Pan family of Shanghai, instanceOf, Ming dynasty lineage]
-
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 emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
-
C.
Yuan dynasty court
The Yuan dynasty court was the central governing institution of the Mongol-ruled Chinese empire, where the emperor and his officials conducted political, military, and ceremonial affairs that integrated Mongol and Chinese traditions.
-
D.
Ming dynasty person
chosen
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.
successor state of the Ming dynasty
The successor state of the Ming dynasty refers to any polity that claimed political, cultural, or dynastic continuity with the Ming after its fall in 1644, such as the Southern Ming regimes or later entities invoking Ming legitimacy.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.