Triple
T3948943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedro IV of Portugal |
E84815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Emperor of Brazil |
C5897
|
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: Emperor of Brazil Context triple: [Pedro IV of Portugal, instanceOf, Emperor of Brazil]
-
A.
emperor of Brazil
chosen
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.
-
B.
King of Portugal
The King of Portugal is the hereditary monarch who historically served as the sovereign ruler and symbolic head of state of the Kingdom of Portugal, overseeing its governance, diplomacy, and colonial expansion until the monarchy’s abolition in 1910.
-
C.
monarch of Mexico
A monarch of Mexico is the sovereign ruler who holds the highest hereditary or elected authority over the Mexican state and its people during a monarchical period.
-
D.
viceroy of the Río de la Plata
The viceroy of the Río de la Plata was the Spanish Crown’s highest colonial authority in the Viceroyalty of the Río de la Plata (covering parts of present-day Argentina, Bolivia, Paraguay, and Uruguay), responsible for governing, administering justice, overseeing the economy, and defending the territory in the late 18th and early 19th centuries.
-
E.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:30 p.m.