Triple
T8311597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantakouzenos dynasty |
E194602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine noble family |
C811
|
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: Byzantine noble family Context triple: [Kantakouzenos dynasty, instanceOf, Byzantine noble family]
-
A.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
-
B.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
C.
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.
-
D.
Milanese patrician family
A Milanese patrician family is a historically prominent, aristocratic lineage from Milan that held social, political, and economic influence within the city’s elite ruling class.
-
E.
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.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.