Triple
T29494382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Wu (Gaozong) |
E748176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Song dynasty noble |
C55811
|
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: Song dynasty noble Context triple: [Empress Wu (Gaozong), instanceOf, Song dynasty noble]
-
A.
Song dynasty empress
A Song dynasty empress is the principal wife of a reigning Song emperor who holds the highest female rank in the imperial court, overseeing palace affairs, ritual duties, and often influencing political and familial succession matters.
-
B.
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.
-
C.
Song dynasty text
A Song dynasty text is a written work produced or compiled during China’s Song dynasty (960–1279), reflecting its era’s distinctive intellectual, literary, religious, and bureaucratic developments.
-
D.
Southern Song emperor
A Southern Song emperor was the hereditary ruler of the Southern Song dynasty (1127–1279) in China, presiding over a reduced but culturally vibrant realm centered in the south after the loss of northern territories to the Jurchen Jin and later facing the Mongol conquest.
-
E.
Song dynasty politician
A Song dynasty politician is an official who served in the governmental and bureaucratic structures of China’s Song dynasty, influencing administration, policy, and state affairs.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:17 p.m.