Triple

T2151528
Position Surface form Disambiguated ID Type / Status
Subject Dickerson v. United States E47190 entity
Predicate statuteInQuestion P8819 FINISHED
Object 18 U.S.C. § 3501 LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 18 U.S.C. § 3501 | Statement: [Dickerson v. United States, statuteInQuestion, 18 U.S.C. § 3501]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statuteInQuestion
Context triple: [Dickerson v. United States, statuteInQuestion, 18 U.S.C. § 3501]
  • A. statuteInvolved chosen
    Indicates that a particular statute or legal provision is implicated, referenced, or applied in relation to a given case, event, or legal matter.
  • B. statuteName
    Indicates the specific legal statute or act by which something is formally designated, governed, or referenced.
  • C. statuteInterpreted
    Indicates that a legal authority (such as a court or agency) has provided an interpretation or authoritative reading of a particular statute.
  • D. stateLawAtIssue
    Indicates that a particular state law is the subject of dispute, analysis, or determination in a given legal context or case.
  • E. establishedByStatute
    Indicates that something has been formally created, defined, or authorized through a specific law or statute.
  • F. None of above.

Provenance (3 batches)

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_69a88a1933e0819094f18426ed74180f completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbe4747a0819080e2234f3ea8995f completed March 7, 2026, 5:57 a.m.
PD Predicate disambiguation batch_69abbd9a60648190b20b116be5c7ad98 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:44 p.m.