Triple
T994999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higher Regional Court of Nuremberg |
E21475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher regional court |
C1421
|
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: higher regional court Context triple: [Higher Regional Court of Nuremberg, instanceOf, higher regional court]
-
A.
intermediate appellate court system
chosen
An intermediate appellate court system is a tier of courts between trial courts and the highest court that reviews lower court decisions for legal errors, ensuring consistency and fairness in the application of law.
-
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.
court of last resort
The court of last resort is the highest judicial authority in a legal system whose decisions are final and cannot be appealed to any higher court.
-
D.
supranational court
A supranational court is a judicial body established by multiple states or international organizations with authority to interpret and apply shared legal norms and issue binding decisions that transcend individual national legal systems.
-
E.
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.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.