Triple
T372969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congressional Budget Office |
E8308
|
entity |
| Predicate | typeOfBudgetOffice |
P5164
|
FINISHED |
| Object | legislative branch budget office |
—
|
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: legislative branch budget office | Statement: [Congressional Budget Office, typeOfBudgetOffice, legislative branch budget office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBudgetOffice Context triple: [Congressional Budget Office, typeOfBudgetOffice, legislative branch budget office]
-
A.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
B.
budgetUnit
Indicates that one entity functions as the budgetary unit or cost-accounting unit associated with another entity within a financial or organizational context.
-
C.
departmentType
Indicates the classification or category of a department, specifying what kind of department it is.
-
D.
hasOfficeType
chosen
Indicates that an entity’s office is classified as a specific type or category of office.
-
E.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec018d508190b5687a9ba90b3092 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.