Triple
T32598415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedwig of Saxony |
E833292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 10th-century German noble |
C35962
|
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: 10th-century German noble Context triple: [Hedwig of Saxony, instanceOf, 10th-century German noble]
-
A.
10th-century German noblewoman
A 10th-century German noblewoman was an aristocratic woman in the fragmented realms of the early Holy Roman Empire, whose status, landholdings, and dynastic marriages played key roles in regional power, inheritance, and political alliances.
-
B.
10th-century German person
chosen
A 10th-century German person is an individual who lived in the German-speaking regions of Central Europe between 900 and 999 CE, shaped by the political, social, and cultural dynamics of the early Holy Roman Empire.
-
C.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
D.
13th-century German noblewoman
A 13th-century German noblewoman is an aristocratic woman of the Holy Roman Empire who managed estates, upheld family alliances through marriage, and navigated the social, legal, and religious structures of medieval German nobility.
-
E.
11th-century Swiss noble
An 11th-century Swiss noble is a high-ranking landowning aristocrat from the region of present-day Switzerland, wielding military, judicial, and economic power within a feudal hierarchy under larger dynastic or ecclesiastical authorities.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.