Triple
T3158986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional and Social Law Chambers |
E66058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized chamber of a supreme court |
C10005
|
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: specialized chamber of a supreme court Context triple: [Constitutional and Social Law Chambers, instanceOf, specialized chamber of a supreme court]
-
A.
chamber of a supreme court
chosen
A chamber of a supreme court is the formal, often architecturally significant room where the court’s justices convene to hear arguments, deliberate, and issue decisions on the highest-level legal matters.
-
B.
special court
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
C.
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.
-
D.
superior court of record
A superior court of record is a higher-level judicial body whose proceedings are formally recorded and preserved, and whose decisions serve as binding legal precedent for lower courts.
-
E.
secret court
A secret court is a judicial body that conducts its proceedings privately, often with restricted access to information, participants, and outcomes, typically for reasons of national security or sensitive matters.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:05 p.m.