Triple
T4267615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Supreme Court cases of the Burger Court |
E96863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection of court decisions |
C12840
|
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: collection of court decisions Context triple: [United States Supreme Court cases of the Burger Court, instanceOf, collection of court decisions]
-
A.
court decision
A court decision is a formal, authoritative ruling issued by a judicial body that resolves the legal issues in a case and may establish or apply legal precedent.
-
B.
United States Supreme Court case collection
chosen
A United States Supreme Court case collection is an organized compilation of decisions, opinions, and related materials from the U.S. Supreme Court, typically indexed and structured for legal research, reference, and historical analysis.
-
C.
early compilation of U.S. Supreme Court decisions
An early compilation of U.S. Supreme Court decisions is a historical collection that systematically gathers, organizes, and publishes the Court’s opinions and rulings from its formative years.
-
D.
jurisprudence corpus
A jurisprudence corpus is a structured collection of legal texts, such as statutes, case law, and scholarly writings, compiled for analysis, research, and reference in the study and practice of law.
-
E.
courtscraper
courtscraper is a tool or library that programmatically collects, parses, and structures data from online court records and dockets.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:07 p.m.