Triple
T930201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Appropriations Act, 2023 |
E20073
|
entity |
| Predicate | containsSpendingFor |
P20937
|
FINISHED |
| Object | defense programs |
—
|
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: defense programs | Statement: [Consolidated Appropriations Act, 2023, containsSpendingFor, defense programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpendingFor Context triple: [Consolidated Appropriations Act, 2023, containsSpendingFor, defense programs]
-
A.
authorizedSpending
Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
-
B.
hasMonetaryComponent
chosen
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
C.
moneyBillsRestriction
Indicates a limitation or control placed on the use, amount, or handling of money bills in a given context.
-
D.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
E.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b349b3d0819090c58b4fb60c6a1b |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.