Triple
T7362733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrera family |
E169790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chilean aristocratic family |
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: Chilean aristocratic family Context triple: [Carrera family, instanceOf, Chilean aristocratic family]
-
A.
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.
-
B.
Dutch patrician family
A Dutch patrician family is a historically prominent, often urban-based lineage belonging to the higher bourgeois elite of the Netherlands, distinguished by long-standing social status, wealth, and influence in commerce, politics, or culture.
-
C.
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.
-
D.
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.
-
E.
Colombian family
A Colombian family is a close-knit group of relatives, often spanning multiple generations, whose relationships, traditions, and daily life are shaped by Colombia’s diverse cultural, regional, and social influences.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:06 p.m.