Triple
T22317541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oda |
E551686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Saxon aristocracy |
C12971
|
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: member of the Saxon aristocracy Context triple: [Oda, instanceOf, member of the Saxon aristocracy]
-
A.
House of Wessex member
A House of Wessex member is an individual belonging to the early medieval royal dynasty that ruled the Anglo-Saxon kingdom of Wessex and later much of England.
-
B.
member of the Norman nobility
A member of the Norman nobility is an individual belonging to the hereditary warrior-aristocratic elite of Norman society, holding land, titles, and political influence derived from feudal bonds and conquest.
-
C.
member of German nobility
chosen
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
D.
member of the Burgundian nobility
A member of the Burgundian nobility is an individual belonging to the hereditary aristocratic elite of the historical Duchy or County of Burgundy, holding land, titles, and social privileges within its feudal hierarchy.
-
E.
Ottonian dynasty member
An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.