Triple
T655482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briggs v. Elliott |
E11638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal court case |
C732
|
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: United States federal court case Context triple: [Briggs v. Elliott, instanceOf, United States federal court case]
-
A.
United States Supreme Court case
chosen
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.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
C.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
D.
United States federal statute
A United States federal statute is a law formally enacted by Congress and signed by the President (or passed over a veto) that applies nationwide and governs conduct, rights, and obligations under federal jurisdiction.
-
E.
United States federal government action
A United States federal government action is any formal decision, policy, regulation, enforcement measure, or operation undertaken by a federal branch or agency under constitutional or statutory authority to influence public affairs or implement federal law.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.