Triple
T2663401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State of Colombia |
E54776
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial body of Colombia |
C6641
|
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: judicial body of Colombia Context triple: [Council of State of Colombia, instanceOf, judicial body of Colombia]
-
A.
Judicial body
chosen
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
B.
department of Colombia
A department of Colombia is a primary administrative division of the country, similar to a state or province, governed by a departmental government with a capital city.
-
C.
organ of the International Court of Justice
An organ of the International Court of Justice is an institutional component of the Court, such as the plenary body of judges, chambers, or administrative units, that performs specific judicial or administrative functions essential to the Court’s operation.
-
D.
principal judicial organ of the United Nations
The principal judicial organ of the United Nations is the International Court of Justice, which settles legal disputes between states and gives advisory opinions on international legal questions in accordance with international law.
-
E.
quasi‑judicial body
A quasi-judicial body is an administrative or regulatory entity that has powers and procedures resembling those of a court, enabling it to interpret laws, conduct hearings, and make binding decisions or recommendations in specific areas of public or private disputes.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.