Triple
T38291996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Noguk |
E1022384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yuan dynasty princess |
C19943
|
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: Yuan dynasty princess Context triple: [Queen Noguk, instanceOf, Yuan dynasty princess]
-
A.
Tang dynasty princess
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.
Mongol princess
chosen
A Mongol princess is a high-born woman of the Mongol imperial or noble lineage, whose status, marriages, and political alliances significantly influence tribal unity, diplomacy, and succession within the Mongol realm.
-
C.
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.
-
D.
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.
-
E.
Mongol empress consort
A Mongol empress consort is the principal wife of a Mongol khan or emperor, holding significant political, diplomatic, and domestic authority within the imperial court and broader empire.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.