Triple

T335448
Position Surface form Disambiguated ID Type / Status
Subject Enabling Act of 1933 E6714 entity
Predicate limitedJudicialReview P8832 FINISHED
Object yes 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: yes | Statement: [Enabling Act of 1933, limitedJudicialReview, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedJudicialReview
Context triple: [Enabling Act of 1933, limitedJudicialReview, yes]
  • A. judicialReviewBy
    Indicates that a judicial body examines and evaluates the legality or constitutionality of an action, decision, or rule made by another authority.
  • B. limitedByCourtCase chosen
    Indicates that one entity’s scope, effect, or applicability is restricted or constrained as a result of a specific court case or legal proceeding.
  • C. standardOfReview
    Indicates the level and type of scrutiny an authority (such as a court or reviewer) applies when evaluating a prior decision, action, or finding.
  • D. bindingNatureOfJudgments
    Indicates that judgments or decisions have a compulsory, legally enforceable effect on the parties or entities to which they apply.
  • E. restriction
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eac81c0c8190b3cb0d53b1cf62b5 completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94f049881908f10bb6548a8bb2e completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.