Triple
T6204378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captaincy of Ceará |
E138711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | captaincy of Brazil |
C19417
|
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: captaincy of Brazil Context triple: [Captaincy of Ceará, instanceOf, captaincy of Brazil]
-
A.
King of Brazil
The King of Brazil is a hypothetical or historical monarch who serves as the sovereign ruler and symbolic head of state of Brazil within a monarchical system of government.
-
B.
constable of Portugal
The constable of Portugal was a high-ranking medieval and early modern royal officer responsible for commanding the kingdom’s armies and overseeing military justice and organization.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:20 p.m.