Triple
T4307702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadiani family |
E93995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian noble dynasty |
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: Georgian noble dynasty Context triple: [Dadiani family, instanceOf, Georgian noble dynasty]
-
A.
Georgian family
A Georgian family is a close-knit household typically spanning multiple generations, characterized by strong traditions, deep respect for elders, and warm hospitality rooted in Georgian culture.
-
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.
German princely dynasty
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.
-
D.
Russian royalty
Russian royalty refers to the hereditary ruling families and nobility of Russia, including tsars, emperors, and their extended dynasties, who held political, social, and cultural power from the medieval period until the early 20th century.
-
E.
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.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:11 p.m.