Triple

T24355167
Position Surface form Disambiguated ID Type / Status
Subject Montejo family E613900 entity
Predicate instanceOf P0 FINISHED
Object Spanish colonial family C48374 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: Spanish colonial family
Context triple: [Montejo family, instanceOf, Spanish colonial family]
  • A. 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.
  • B. Spanish family
    A Spanish family is a social unit typically characterized by close-knit relationships, strong intergenerational ties, and cultural traditions centered around shared meals, celebrations, and mutual support.
  • C. 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.
  • D. Spanish colonial settlement
    A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
  • E. Guatemalan elite family
    A Guatemalan elite family is a socially and economically powerful kinship group that concentrates wealth, political influence, and cultural prestige, often spanning generations and shaping national institutions and networks.
  • 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_69e2d7ddd29481909e7f539a6072bd71 completed April 18, 2026, 1:01 a.m.
Created at: April 18, 2026, 1:59 a.m.