Triple
T9552454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gisela of Swabia |
E230454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Salian dynasty consort |
C26002
|
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: Salian dynasty consort Context triple: [Gisela of Swabia, instanceOf, Salian dynasty consort]
-
A.
Isaurian dynasty ruler
An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
-
B.
Vijayanagara royal consort
A Vijayanagara royal consort is a queen or principal spouse of a Vijayanagara emperor, holding ceremonial, political, and dynastic significance within the imperial court of the Vijayanagara Empire.
-
C.
Mughal empress consort
A Mughal empress consort is the principal wife of a reigning Mughal emperor, holding significant ceremonial status, political influence, and often patronage roles within the imperial court.
-
D.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
E.
Kalhora dynasty ruler
A Kalhora dynasty ruler is a sovereign from the Kalhora family who governed Sindh (in present-day Pakistan) between the early 18th and late 18th centuries, overseeing its political, economic, and cultural 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:02 p.m.