Triple
T20982745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aycinena family |
E516805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Guatemalan elite family |
C44158
|
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: Guatemalan elite family Context triple: [Aycinena family, instanceOf, Guatemalan elite family]
-
A.
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.
-
B.
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.
-
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 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.
-
E.
Mesoamerican nobility
Mesoamerican nobility comprised the hereditary elite classes of pre-Columbian societies, who held political, religious, and military authority, controlled land and tribute, and maintained social hierarchy through lineage, ritual, and alliance.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:48 p.m.