Triple
T23265436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reclamation Fund |
E588132
|
entity |
| Predicate | expendituresAuthorizedBy |
P27313
|
FINISHED |
| Object | annual appropriations acts |
—
|
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: annual appropriations acts | Statement: [Reclamation Fund, expendituresAuthorizedBy, annual appropriations acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expendituresAuthorizedBy Context triple: [Reclamation Fund, expendituresAuthorizedBy, annual appropriations acts]
-
A.
authorizedAppropriations
chosen
Indicates that a governing body has formally approved the allocation of funds for a specific purpose or activity.
-
B.
authorizedSpending
Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
-
C.
hasBudgetaryAuthorityFrom
Indicates that one entity possesses formal power or permission, granted by another entity, to make or control budgetary or financial allocation decisions.
-
D.
overseesSpendingOf
Indicates that one entity has authority to monitor, direct, or control how another entity’s funds or budget are used.
-
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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:34 p.m.