Triple
T9727602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerberga of Saxony |
E235654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval queen consort |
C1060
|
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: medieval queen consort Context triple: [Gerberga of Saxony, instanceOf, medieval queen consort]
-
A.
12th-century English queen consort
A 12th-century English queen consort is the wife of an English king during the 1100s, serving as a political partner, dynastic link, and influential figure in courtly, diplomatic, and sometimes religious affairs.
-
B.
queen consort
chosen
A queen consort is the wife of a reigning king who holds the title of queen through marriage, typically without sovereign ruling authority.
-
C.
Duchess consort of Lancaster
The Duchess consort of Lancaster is the wife of the Duke of Lancaster, holding the title by marriage and often participating in the social, ceremonial, and dynastic roles associated with the ducal house of Lancaster.
-
D.
Countess consort of Champagne
A Countess consort of Champagne is the wife of the reigning Count of Champagne, holding the title and associated social and ceremonial duties by marriage rather than by hereditary right.
-
E.
Bavarian queen consort
A Bavarian queen consort is the wife of a reigning king of Bavaria, holding the ceremonial and social role of queen without exercising sovereign authority.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:21 p.m.