Triple
T16115397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri v. McNeely |
E390989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | search and seizure case |
C36996
|
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: search and seizure case Context triple: [Missouri v. McNeely, instanceOf, search and seizure case]
-
A.
Miranda doctrine case
A Miranda doctrine case is a legal case that addresses the application, scope, or interpretation of the constitutional requirement that law enforcement advise individuals of their rights (such as the right to remain silent and to an attorney) before custodial interrogation.
-
B.
Third Amendment case
A Third Amendment case is a legal dispute that centers on whether the government has violated the constitutional prohibition against quartering soldiers in private homes without the owner’s consent, particularly in times of peace.
-
C.
extradition case
An extradition case is a legal proceeding in which one jurisdiction formally requests and seeks the surrender of a person from another jurisdiction to face criminal charges or serve a sentence.
-
D.
fugitive slave law case
A fugitive slave law case is a legal proceeding arising from the capture, return, or status of an escaped enslaved person under statutes mandating the recovery of individuals fleeing enslavement.
-
E.
fugitive slave case
A fugitive slave case is a legal proceeding in which an enslaved person who has escaped from a slaveholding jurisdiction is pursued, captured, and adjudicated under laws governing the return of escaped slaves.
- F. None of above. chosen
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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.