Triple
T2236519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Luxembourg |
E49293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval European dynasty |
C810
|
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 European dynasty Context triple: [House of Luxembourg, instanceOf, medieval European dynasty]
-
A.
dynastic empire
A dynastic empire is a vast, centralized state ruled over generations by a single family lineage that legitimizes its authority through hereditary succession and often divine or traditional claims to power.
-
B.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
-
C.
dynasty
chosen
A dynasty is a succession of rulers or leaders from the same family or lineage, often maintaining power over multiple generations within a state or organization.
-
D.
Plantagenet king
A Plantagenet king is a medieval English monarch from the Plantagenet dynasty, ruling between the mid-12th and late 15th centuries and known for shaping the development of English law, governance, and territorial power.
-
E.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.