Triple

T26658911
Position Surface form Disambiguated ID Type / Status
Subject H.R. 1424 E666584 entity
Predicate authorizesSpendingUpTo P7930 FINISHED
Object 700 billion United States dollars 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: 700 billion United States dollars | Statement: [H.R. 1424, authorizesSpendingUpTo, 700 billion United States dollars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: authorizesSpendingUpTo
Context triple: [H.R. 1424, authorizesSpendingUpTo, 700 billion United States dollars]
  • A. authorizedSpending chosen
    Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
  • B. monetaryLimit
    Indicates a constraint or maximum allowable amount of money associated with an action, transaction, or relationship.
  • C. overseesSpendingOf
    Indicates that one entity has authority to monitor, direct, or control how another entity’s funds or budget are used.
  • D. spendingRequires
    Indicates that performing a spending action is contingent upon satisfying a specified requirement or condition.
  • E. authorizedBudget
    Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
  • 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_69ee9cf8c7188190b9b00270a8a89164 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6bbf6e33c819086e5176d64e7a614 completed May 3, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69f6ba6b1e6c8190adf9d6a257e0b744 completed May 3, 2026, 3 a.m.
Created at: April 27, 2026, 2:36 a.m.