Triple
T21140218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Courts of Brazil |
E520909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Judiciary of Brazil |
C44591
|
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: branch of the Judiciary of Brazil Context triple: [Military Courts of Brazil, instanceOf, branch of the Judiciary of Brazil]
-
A.
federal government body of Brazil
A federal government body of Brazil is an official institution or agency that operates under the authority of the Brazilian federal government to implement national policies, administer public services, and regulate specific sectors across the country.
-
B.
federative unit of Brazil
A federative unit of Brazil is a primary political and administrative division of the country—such as a state or the Federal District—with its own government, constitution, and limited autonomy under the Brazilian federal system.
-
C.
Brazilian law
Brazilian law is the legal system of Brazil, based on civil law traditions and the Federal Constitution of 1988, governing the rights, duties, and relationships of individuals, organizations, and the state.
-
D.
municipality of Brazil
A municipality of Brazil is the smallest autonomous administrative division in the country, governed by a mayor and municipal council, responsible for local public services, regulations, and development within its defined territory.
-
E.
branch court
A branch court is a subsidiary judicial facility or division located away from a main courthouse to provide more accessible legal services within a specific geographic area.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.