Triple

T616420
Position Surface form Disambiguated ID Type / Status
Subject Craig v. Boren E14413 entity
Predicate standardOfReviewEstablished P3850 FINISHED
Object intermediate scrutiny 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: intermediate scrutiny | Statement: [Craig v. Boren, standardOfReviewEstablished, intermediate scrutiny]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardOfReviewEstablished
Context triple: [Craig v. Boren, standardOfReviewEstablished, intermediate scrutiny]
  • A. standardOfReview chosen
    Indicates the level and type of scrutiny an authority (such as a court or reviewer) applies when evaluating a prior decision, action, or finding.
  • B. standardOfProof
    Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
  • C. reviewedBy
    Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
  • D. establishedFollowing
    Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
  • E. establishedAs
    Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
  • 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_69a4934b17c881909ace8270e8ddd202 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49e22f3688190a512bec3f0347814 completed March 1, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69a49cfd15288190b4abdbd0bce3edcd completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.