Triple
T4377433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billung dynasty |
E99040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval German dynasty |
C12506
|
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 German dynasty Context triple: [Billung dynasty, instanceOf, medieval German dynasty]
-
A.
German princely dynasty
chosen
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
B.
House of Wettin
The House of Wettin is a historic European noble dynasty originating in Saxony that produced numerous princes, electors, kings, and other rulers across central and northern Europe from the Middle Ages onward.
-
C.
Polish dynasty
A Polish dynasty is a hereditary ruling family originating from Poland that holds political power and influence over the country or its territories across successive generations.
-
D.
Habsburg
Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
-
E.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:18 p.m.