Triple
T4783811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azpilicueta |
E106428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Basque-language surname |
C17408
|
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-language surname Context triple: [Azpilicueta, instanceOf, Basque-language surname]
-
A.
Spanish-language surname
A Spanish-language surname is a family name of Spanish origin or usage, often reflecting ancestry, geography, occupation, or personal characteristics within Spanish-speaking cultures.
-
B.
Portuguese-language surname
A Portuguese-language surname is a family name originating from Portuguese linguistic and cultural traditions, typically used to identify lineage, heritage, or geographic roots within Portuguese-speaking communities.
-
C.
Polish-language surname
A Polish-language surname is a family name originating from the Polish language, often reflecting ancestry, occupation, geography, or personal characteristics within Polish cultural and linguistic traditions.
-
D.
Hebrew-language surname
A Hebrew-language surname is a family name derived from or adapted into the Hebrew language, often reflecting Hebrew words, biblical names, places, or cultural-historical origins within Jewish communities.
-
E.
Gaelic-language surname
A Gaelic-language surname is a family name originating from the Gaelic languages (such as Irish or Scottish Gaelic), typically reflecting ancestral lineage, occupation, or geographic origin through traditional Gaelic naming conventions.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:22 p.m.