Triple
T23031043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Councilor of State of the Empire of Brazil |
E573456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial Brazilian office |
C4989
|
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: imperial Brazilian office Context triple: [Councilor of State of the Empire of Brazil, instanceOf, imperial Brazilian office]
-
A.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
B.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
C.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
-
D.
captaincy of Brazil
The captaincy of Brazil was a hereditary Portuguese colonial administrative division established in the 16th century to govern and develop portions of the territory that would become modern Brazil.
-
E.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:53 p.m.