Triple
T32799069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visconde de Pirajá |
E838846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian nobleman |
C60869
|
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: Brazilian nobleman Context triple: [Visconde de Pirajá, instanceOf, Brazilian nobleman]
-
A.
Brazilian prince
A Brazilian prince is a male member of the Brazilian imperial family, historically holding a dynastic title linked to the former Empire of Brazil and its line of succession.
-
B.
Venezuelan aristocrat
A Venezuelan aristocrat is a member of the traditional upper class in Venezuela, typically characterized by inherited wealth, social prestige, and influence rooted in colonial-era landownership and elite family networks.
-
C.
Mexican nobleman
A Mexican nobleman is a male member of the hereditary aristocracy in Mexico, historically holding titles, land, and social privileges often rooted in colonial or pre-colonial lineage.
-
D.
Ecuadorian nobleman
An Ecuadorian nobleman is a male member of the traditional aristocracy of Ecuador, historically distinguished by inherited titles, landownership, and social prestige within the country's colonial and post-colonial elite.
-
E.
14th-century Portuguese noble
A 14th-century Portuguese noble is a high-ranking member of the medieval Portuguese aristocracy who held land, exercised local political and military authority, and played a key role in the kingdom’s dynastic, feudal, and courtly affairs.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.