Triple
T26369187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Song |
E660724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Dynasties dynasty |
C51469
|
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: Southern Dynasties dynasty Context triple: [Liu Song, instanceOf, Southern Dynasties dynasty]
-
A.
Southern Dynasty
Southern Dynasty is a conceptual class representing a historical or fictional ruling lineage associated with the southern region of a realm, characterized by its distinct cultural, political, and territorial identity.
-
B.
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.
-
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.
regime of the Five Dynasties and Ten Kingdoms period
A regime of the Five Dynasties and Ten Kingdoms period is a short-lived, regionally based political state that ruled parts of China between the late Tang collapse and the Song unification, typically characterized by fragmented authority, shifting alliances, and frequent dynastic change.
-
E.
Jin dynasty emperor
A Jin dynasty emperor is the supreme hereditary ruler of the Jurchen-led Jin dynasty in northern China (1115–1234), holding ultimate political, military, and ritual authority over the state and its subjects.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:57 p.m.