Triple
T15290832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Cheng |
E365521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty princely title |
C2528
|
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 princely title Context triple: [Prince of Cheng, instanceOf, Ming dynasty princely title]
-
A.
Qing dynasty prince
A Qing dynasty prince is a male member of the imperial Aisin Gioro clan who holds a hereditary noble title within the hierarchical peerage system of the Qing Empire, often bearing political, military, or ceremonial responsibilities.
-
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.
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.
-
D.
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.
-
E.
princely office
chosen
A princely office is an institutional role or position held by a prince or princely figure, encompassing the authority, duties, and ceremonial functions associated with governing or representing a principality or royal domain.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.