Triple
T16101480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaccine Rules of the United States Court of Federal Claims |
E390630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized court rules |
C5085
|
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 court rules Context triple: [Vaccine Rules of the United States Court of Federal Claims, instanceOf, specialized court rules]
-
A.
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.
-
B.
judicial rules
chosen
Judicial rules are formal guidelines and procedures established by courts to govern how legal cases are processed, decided, and managed within the judicial system.
-
C.
subdivision of court
A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
-
D.
specialized criminal law
Specialized criminal law is a focused area of legal practice that deals with specific categories of criminal offenses, such as white-collar crime, cybercrime, or organized crime, requiring in-depth expertise in the relevant statutes, procedures, and investigative methods.
-
E.
segment of the California Rules of Court
A segment of the California Rules of Court is a distinct, formally numbered provision or subsection that prescribes specific procedural or administrative requirements governing court practice within California’s judicial system.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.