Triple
T32945448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Taiping |
E842787
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tang dynasty princess |
C60086
|
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: Tang dynasty princess Context triple: [Princess Taiping, instanceOf, Tang dynasty princess]
-
A.
Tang dynasty princess
chosen
A Tang dynasty princess is an imperial daughter of the Tang royal family who embodies the era’s political prestige, cultural refinement, and complex courtly alliances through her status, marriages, and patronage.
-
B.
Tang dynasty prince
A Tang dynasty prince is a male member of the imperial family of China’s Tang dynasty, typically holding noble titles, political influence, and responsibilities in governance, military affairs, or regional administration.
-
C.
Han dynasty princess
A Han dynasty princess is an imperial daughter or close female relative of the Han emperor, whose status, marriages, and political roles were used to secure alliances, consolidate power, and embody the prestige of the ruling house in ancient China.
-
D.
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.
-
E.
Korean princess
A Korean princess is a royal female member of Korea’s monarchy, traditionally embodying noble lineage, cultural refinement, and responsibilities in courtly, diplomatic, and ceremonial life.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.