Triple
T16713902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 111-152 |
E406174
|
entity |
| Predicate | usedBudgetReconciliation |
P124340
|
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: [Public Law 111-152, usedBudgetReconciliation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBudgetReconciliation Context triple: [Public Law 111-152, usedBudgetReconciliation, yes]
-
A.
authorizedBudget
Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
-
B.
usesSalaryBudgets
Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
-
C.
budgetAccount
Indicates a relationship where an entity is associated with, charged to, or managed under a specific budget account for financial tracking or allocation.
-
D.
budgetingSystem
Indicates a system or process used to plan, allocate, track, and control financial resources or budgets.
-
E.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38653cdd48190863e1cc989e21f39 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.