Triple
T24767411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Jasso y Azpilicueta |
E619622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Basque noble family |
C40608
|
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: Basque noble family Context triple: [de Jasso y Azpilicueta, instanceOf, Basque noble family]
-
A.
Basque noble lineage
chosen
A Basque noble lineage is a hereditary aristocratic family originating from the Basque Country, defined by shared ancestry, territorial ties, and enduring social prestige within regional historical and political structures.
-
B.
Portuguese noble family
A Portuguese noble family is a lineage of aristocratic individuals in Portugal, historically endowed with hereditary titles, privileges, and social status, often tied to landownership, political influence, and service to the Crown.
-
C.
Occitan noble family
An Occitan noble family is a lineage of aristocratic households originating from the historical Occitania region in southern Europe, distinguished by hereditary titles, landholdings, and regional cultural influence.
-
D.
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.
-
E.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:28 a.m.