Triple
T30555920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Borovsk |
E777697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Russian noble family |
C56276
|
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 Russian noble family Context triple: [House of Borovsk, instanceOf, medieval Russian noble family]
-
A.
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.
-
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.
16th-century Russian nobility
16th-century Russian nobility were hereditary elites who held land, military and administrative authority, and significant influence at the tsar’s court within the evolving centralized Muscovite state.
-
D.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
E.
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.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:20 p.m.