Triple
T4824757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galen Black |
E107795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | party to a United States Supreme Court case |
C12445
|
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: party to a United States Supreme Court case Context triple: [Galen Black, instanceOf, party to a United States Supreme Court case]
-
A.
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.
-
B.
supreme court
The Supreme Court is the highest judicial authority in a legal system, responsible for interpreting the constitution, resolving significant legal disputes, and setting binding precedents for lower courts.
-
C.
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.
-
D.
named party in court case
chosen
A named party in a court case is an individual or entity explicitly identified in legal proceedings as having a direct legal interest in the outcome, such as a plaintiff, defendant, petitioner, or respondent.
-
E.
United States Supreme Court case collection
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.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.