Triple
T569806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Court of Appeals for the Armed Forces |
E13636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized appellate court |
C767
|
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 appellate court Context triple: [United States Court of Appeals for the Armed Forces, instanceOf, specialized appellate court]
-
A.
special court
chosen
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.
-
B.
intermediate appellate court system
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.
-
C.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
D.
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.
-
E.
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.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:33 p.m.