Triple
T15169237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurieli dynasty |
E362441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian noble family |
C36052
|
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 family Context triple: [Gurieli dynasty, instanceOf, Georgian noble family]
-
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.
member of the Georgian nobility
A member of the Georgian nobility is an individual belonging to the hereditary aristocratic class of Georgia, historically endowed with land, titles, and social privileges within the Georgian feudal and royal systems.
-
C.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
D.
Romanian noble house
A Romanian noble house is a historically significant aristocratic family from the Romanian principalities, distinguished by hereditary titles, landholdings, and political or cultural influence.
-
E.
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.
- F. None of above. chosen
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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:08 a.m.