Triple
T11782622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Pedro de Alcântara of Orléans-Braganza |
E280187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | head of the Petrópolis branch of the Brazilian imperial family |
C29085
|
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: head of the Petrópolis branch of the Brazilian imperial family Context triple: [Prince Pedro de Alcântara of Orléans-Braganza, instanceOf, head of the Petrópolis branch of the Brazilian imperial family]
-
A.
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.
-
B.
Brazilian princess
A Brazilian princess is a female member of Brazil’s former imperial family, historically holding royal title and status within the Brazilian Empire’s monarchical hierarchy.
-
C.
Empress consort of Brazil
The Empress consort of Brazil was the wife of the reigning Emperor of Brazil, serving as the empire’s foremost female royal figure with ceremonial, social, and dynastic responsibilities but no sovereign authority.
-
D.
emperor of Brazil
The emperor of Brazil was the hereditary monarch and head of state of the Empire of Brazil, wielding executive, legislative, and symbolic authority from 1822 to 1889.
-
E.
head of a royal house
chosen
The head of a royal house is the individual who holds the highest hereditary authority within a royal family, often serving as its symbolic leader, custodian of traditions, and primary representative in dynastic matters.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.