Triple
T37068782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Ataíde |
E917519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese noble family name |
C25690
|
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: Portuguese noble family name Context triple: [de Ataíde, instanceOf, Portuguese noble family name]
-
A.
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.
-
B.
Portuguese noble family
chosen
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.
Portuguese family
A Portuguese family is a close-knit household unit rooted in Portuguese culture, typically characterized by strong intergenerational bonds, shared traditions, and a deep emphasis on communal meals and gatherings.
-
D.
Portuguese appellation
A Portuguese appellation is a legally defined and protected geographical indication used to designate wines or other agricultural products originating from specific regions of Portugal that meet established quality and production standards.
-
E.
Portuguese-language given name
A Portuguese-language given name is a personal first name used primarily by Portuguese speakers, often reflecting Lusophone cultural, religious, or historical influences.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.