Triple
T9062579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Budget and Analytics |
E217162
|
entity |
| Predicate | typeOfBudgetWork |
P1366
|
FINISHED |
| Object | budget development |
—
|
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: budget development | Statement: [Office of Budget and Analytics, typeOfBudgetWork, budget development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBudgetWork Context triple: [Office of Budget and Analytics, typeOfBudgetWork, budget development]
-
A.
typeOfBudgetRole
Indicates that one entity functions as a specific budget-related role or responsibility type in relation to another entity.
-
B.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
C.
budgetItemOf
Indicates that one entity is a specific budget line or allocation that belongs to, or is part of, another entity’s overall budget.
-
D.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
E.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ecd352c8190a744579209b2e535 |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.