Triple
T20331123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Christina of Saxony |
E492482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Saxon princess |
C43659
|
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: Saxon princess Context triple: [Maria Christina of Saxony, instanceOf, Saxon princess]
-
A.
Lombard princess
A Lombard princess is a noblewoman of royal blood from the Lombard kingdoms of early medieval Italy, often serving as a key figure in dynastic alliances, courtly politics, and the transmission of cultural and religious influence.
-
B.
Mitanni princess
A Mitanni princess is a royal woman from the ancient Hurrian-speaking kingdom of Mitanni, typically involved in dynastic marriages, political alliances, and the cultural life of the Late Bronze Age Near East.
-
C.
Frankish princess
A Frankish princess is a royal woman of the Frankish kingdoms, typically a daughter or close female relative of a Frankish king, whose status and marriages often served to secure political alliances and consolidate dynastic power in early medieval Europe.
-
D.
Ottonian princess
An Ottonian princess is a noblewoman of the 10th–11th century Ottonian dynasty in the Holy Roman Empire, whose role combined dynastic marriage politics, religious patronage, and the reinforcement of imperial authority.
-
E.
Cappadocian princess
A Cappadocian princess is a noblewoman from the ancient region of Cappadocia, often depicted as a politically influential and culturally sophisticated figure within Hellenistic or Roman-era Anatolian society.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:22 a.m.