Triple
T4849414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent Review Tribunal |
E108374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial body of MERCOSUR |
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 MERCOSUR Context triple: [Permanent Review Tribunal, instanceOf, judicial body of MERCOSUR]
-
A.
principal organ of the Union of South American Nations
The principal organ of the Union of South American Nations is its highest decision-making body responsible for setting the organization’s overall political direction, policies, and priorities among member states.
-
B.
sectoral council of UNASUR
The sectoral council of UNASUR is a specialized body that brings together member states’ ministers and experts in a specific policy area to coordinate regional strategies, harmonize initiatives, and promote integration within that sector across South America.
-
C.
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.
-
D.
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.
-
E.
UNASUR organ
A UNASUR organ is an institutional body within the Union of South American Nations responsible for carrying out specific functions such as decision-making, coordination, or implementation of the organization's policies and initiatives.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.