Triple
T12898692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Egisheim-Dagsburg |
E308559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alsatian noble house |
C32047
|
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: Alsatian noble house Context triple: [House of Egisheim-Dagsburg, instanceOf, Alsatian noble house]
-
A.
medieval French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
-
B.
Breton ducal house
A Breton ducal house is a noble lineage that held or claimed the ducal title in the historical region of Brittany, shaping its political, dynastic, and territorial affairs.
-
C.
House of Hesse and by Rhine
The House of Hesse and by Rhine was a German grand ducal dynasty that ruled the Grand Duchy of Hesse (centered on Darmstadt) from the early 19th century until the end of the German monarchies in 1918.
-
D.
member of the House of Lorraine
A member of the House of Lorraine is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled the Duchy of Lorraine and later held significant royal and imperial titles.
-
E.
Prussian aristocratic family
A Prussian aristocratic family is a noble lineage rooted in the historical Kingdom of Prussia, characterized by hereditary titles, landed estates, military and bureaucratic service, and adherence to traditional social hierarchies and customs.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:40 p.m.