Triple
T7452810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Desk |
E172046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial coordination body |
C4392
|
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 coordination body Context triple: [National Desk, instanceOf, judicial coordination body]
-
A.
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.
-
B.
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.
-
C.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
D.
Judicial conference committee
chosen
A judicial conference committee is a group of judges and related officials convened to study, discuss, and recommend policies or rules to improve the administration and operation of the court system.
-
E.
intelligence coordination body
An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security objectives.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:14 p.m.