Triple
T22307165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infante Henry, Duke of Viseu |
E551409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Aviz member |
C12882
|
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: House of Aviz member Context triple: [Infante Henry, Duke of Viseu, instanceOf, House of Aviz member]
-
A.
member of the House of Aviz
chosen
A member of the House of Aviz is an individual belonging to the Portuguese royal dynasty that ruled Portugal from 1385 to 1580, known for consolidating national independence and leading the Age of Discoveries.
-
B.
House of Braganza member
A House of Braganza member is an individual belonging by birth or legitimate dynastic connection to the Portuguese royal and noble family of Braganza, historically associated with the thrones of Portugal and Brazil.
-
C.
member of the House of Trastámara
A member of the House of Trastámara is an individual belonging to the late medieval and early modern Iberian royal dynasty that ruled Castile, Aragon, and later a unified Spain, as well as other European territories.
-
D.
House of Habsburg member
A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
-
E.
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.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.