Triple
T14472426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Drăculești |
E358877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Romanian princely 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 Romanian princely dynasty Context triple: [House of Drăculești, instanceOf, medieval Romanian princely dynasty]
-
A.
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.
-
B.
medieval Serbian dynasty
A medieval Serbian dynasty is a ruling family that governed Serbian territories during the Middle Ages, shaping the region’s political, cultural, and religious development through hereditary succession and dynastic alliances.
-
C.
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.
-
D.
Serbian dynasty
A Serbian dynasty is a hereditary ruling family that governed medieval Serbian states, shaping their political, cultural, and territorial development over successive generations.
-
E.
Bulgarian royal dynasty
A Bulgarian royal dynasty is a hereditary ruling family that held the throne of Bulgaria over successive generations, shaping the country's political, cultural, and historical development.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.