Triple
T4993785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Registry of the International Court of Justice |
E112195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial support organ |
C8184
|
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 support organ Context triple: [Registry of the International Court of Justice, instanceOf, judicial support organ]
-
A.
judicial administrative office
chosen
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
B.
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.
-
C.
Judicial body
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
D.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
E.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:34 p.m.