Triple
T3196347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumamoto Branch of Fukuoka High Court |
E66943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial body in Japan |
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 in Japan Context triple: [Kumamoto Branch of Fukuoka High Court, instanceOf, judicial body in Japan]
-
A.
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.
-
B.
subdivision of the Supreme Court of Japan
A subdivision of the Supreme Court of Japan is an internal organizational unit, such as a petty bench or administrative division, that handles specific categories of judicial or administrative functions within the Court.
-
C.
government agency of Japan
A government agency of Japan is an official administrative body established by the Japanese government to implement laws, deliver public services, and manage specific policy areas at the national level.
-
D.
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.
-
E.
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.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:07 p.m.