Triple
T21313561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francisco de Lima e Silva |
E525405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regent of Brazil |
C44675
|
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: regent of Brazil Context triple: [Francisco de Lima e Silva, instanceOf, regent of Brazil]
-
A.
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.
-
B.
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.
-
C.
Queen of Brazil
The Queen of Brazil is a conceptual class representing a sovereign female monarch who embodies the political authority, cultural identity, and ceremonial leadership of a Brazilian kingdom within a given historical or fictional context.
-
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.
former president of Brazil
A former president of Brazil is an individual who previously held the office of head of state and government of the Federative Republic of Brazil, having completed or left their presidential term.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:27 p.m.