Triple
T12678722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC International Court of Arbitration |
E302888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arbitral tribunal |
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: arbitral tribunal Context triple: [ICC International Court of Arbitration, instanceOf, arbitral tribunal]
-
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.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
-
C.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
D.
international claims commission
An international claims commission is a temporary or permanent body established by states or international organizations to adjudicate and resolve financial or property claims arising from disputes, conflicts, or treaty violations across national borders.
-
E.
Permanent Court of Arbitration organ
A Permanent Court of Arbitration organ is an institutional component or body within the Permanent Court of Arbitration responsible for carrying out specific administrative, procedural, or adjudicative functions in the facilitation of international dispute resolution.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.