Triple
T26805534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belosselsky-Belozersky |
E671824
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian princely family |
C4646
|
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: Russian princely family Context triple: [Belosselsky-Belozersky, instanceOf, Russian princely family]
-
A.
Russian royalty
chosen
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.
-
B.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
-
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.
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.
-
E.
British dynasty
A British dynasty is a succession of rulers or influential family members from the same lineage who hold power or prominence in Britain over multiple 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:26 a.m.