Triple

T13768031
Position Surface form Disambiguated ID Type / Status
Subject Omnibus Budget Reconciliation Act of 1986 E330800 entity
Predicate federalDeficitReductionGoal P14665 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: [Omnibus Budget Reconciliation Act of 1986, federalDeficitReductionGoal, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: federalDeficitReductionGoal
Context triple: [Omnibus Budget Reconciliation Act of 1986, federalDeficitReductionGoal, yes]
  • A. federalDeficitReductionMeasure
    Indicates a governmental action or policy specifically intended to decrease the federal budget deficit.
  • B. monetaryPolicyGoal
    Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
  • C. managedFederalDebt
    Indicates that an entity is responsible for overseeing, controlling, or administering the federal government’s debt obligations.
  • D. nationalGoals
    Indicates a relationship where certain objectives or targets are officially set or recognized as the goals of a nation.
  • E. economicGoal chosen
    Indicates that an entity has a targeted economic outcome or objective it aims to achieve.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0233ecc48190b934f085d2501eb1 completed April 14, 2026, 9 a.m.
PD Predicate disambiguation batch_69dbbe97846c819093b00ea117b64e0d completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 10:10 p.m.