Triple

T13555966
Position Surface form Disambiguated ID Type / Status
Subject Omnibus Budget Reconciliation Act of 1981 E323774 entity
Predicate legislativeMechanism P110334 FINISHED
Object budget reconciliation 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: budget reconciliation | Statement: [Omnibus Budget Reconciliation Act of 1981, legislativeMechanism, budget reconciliation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legislativeMechanism
Context triple: [Omnibus Budget Reconciliation Act of 1981, legislativeMechanism, budget reconciliation]
  • A. legislature
    Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
  • B. legislativeActOf
    Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
  • C. legislatureComponent
    Indicates that one entity is a constituent part or chamber of a larger legislative body.
  • D. areaOfLegislation
    Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
  • E. legislatureStructure
    Indicates how a legislative body is organized, such as its internal composition, chambers, and structural arrangement.
  • F. None of above. chosen

Provenance (4 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae13bec4819084c1770638c00ed9 completed April 12, 2026, 2:37 p.m.
PDg Predicate description generation batch_69dbbb8c77dc8190b7bd803b5e168d23 completed April 12, 2026, 3:34 p.m.
Created at: April 9, 2026, 9:47 p.m.