Triple
T18368315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braun family |
E440108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chilean elite family |
C40416
|
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 elite family Context triple: [Braun family, instanceOf, Chilean elite 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.
Argentine family
An Argentine family is a social unit typically characterized by close-knit, multigenerational relationships, strong cultural traditions, and shared values rooted in Argentina’s history, customs, and regional identities.
-
C.
Catalan bourgeois family
A Catalan bourgeois family is a middle- to upper-middle-class household from Catalonia characterized by economic comfort, strong regional identity, and adherence to traditional social, cultural, and often conservative values.
-
D.
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.
-
E.
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.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:38 a.m.