Triple
T19718668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribunal Permanente de Revisión del MERCOSUR |
E473546
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tribunal internacional |
C7772
|
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: tribunal internacional Context triple: [Tribunal Permanente de Revisión del MERCOSUR, instanceOf, tribunal internacional]
-
A.
tribunal
chosen
A tribunal is a formal body or court established to adjudicate disputes, interpret laws or rules, and render binding decisions or judgments.
-
B.
supranational court
A supranational court is a judicial body established by multiple states or international organizations with authority to interpret and apply shared legal norms and issue binding decisions that transcend individual national legal systems.
-
C.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
-
D.
internationalized criminal court
An internationalized criminal court is a hybrid judicial body that combines domestic and international law, personnel, and procedures to prosecute individuals for serious crimes such as war crimes, crimes against humanity, and genocide within a specific country or region.
-
E.
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.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.