Triple
T12783541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engblom v. Carey |
E305566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Court of Appeals case |
C29175
|
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: U.S. Court of Appeals case Context triple: [Engblom v. Carey, instanceOf, U.S. Court of Appeals case]
-
A.
United States Court of Appeals case
chosen
A United States Court of Appeals case is a federal appellate court decision that reviews and resolves legal issues appealed from U.S. district courts or certain federal agencies within its circuit jurisdiction.
-
B.
United States state court case
A United States state court case is a legal dispute adjudicated within a state’s judicial system, governed by that state’s laws and procedures rather than federal law.
-
C.
United States Supreme Court case
A United States Supreme Court case is a legal dispute brought before the highest federal court in the U.S., resulting in a binding decision that interprets the Constitution, federal laws, or treaties and sets nationwide precedent.
-
D.
United States Supreme Court brief
A United States Supreme Court brief is a formal written legal document submitted to the Court that presents a party’s arguments, relevant facts, and supporting authorities to persuade the Justices to rule in that party’s favor.
-
E.
federal jurisdiction case
A federal jurisdiction case is a legal dispute that is heard in a federal court because it involves federal laws, the U.S. Constitution, the federal government, or parties from different states meeting specific jurisdictional requirements.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:29 p.m.