Triple
T12713118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Griffins |
E303770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval ruling dynasty |
C27116
|
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 ruling dynasty Context triple: [House of Griffins, instanceOf, medieval ruling dynasty]
-
A.
medieval ruling family
chosen
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
B.
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.
-
C.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
D.
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.
-
E.
medieval Bulgarian dynasty
A medieval Bulgarian dynasty is a ruling family that governed the Bulgarian state during the Middle Ages, shaping its political structure, territorial expansion, cultural development, and relations with neighboring powers.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:23 p.m.