Triple
T20570696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolívar family |
E505088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Venezuelan noble family |
C43272
|
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: Venezuelan noble family Context triple: [Bolívar family, instanceOf, Venezuelan noble family]
-
A.
Peruvian noble family
A Peruvian noble family is a lineage recognized within Peru’s historical aristocracy, often tracing its ancestry to colonial-era Spanish nobility or indigenous elites and distinguished by inherited titles, social status, and cultural influence.
-
B.
Venezuelan aristocrat
A Venezuelan aristocrat is a member of the traditional upper class in Venezuela, typically characterized by inherited wealth, social prestige, and influence rooted in colonial-era landownership and elite family networks.
-
C.
Mexican noble family
A Mexican noble family is a historically recognized lineage in Mexico that holds or once held hereditary titles, social prestige, and influence, often tied to colonial-era landownership, political power, and cultural patronage.
-
D.
Peruvian noble lineage
A Peruvian noble lineage is a hereditary social class in Peru composed of families that trace their prestige, titles, and status to pre-Columbian indigenous nobility, colonial-era aristocracy, or recognized republican-era elites.
-
E.
Chilean elite family
A Chilean elite family is a socially and economically dominant kinship group that concentrates wealth, political influence, and cultural capital across generations within Chilean society.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.