Triple
T2913864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Management and Budget liaison functions |
E63750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government liaison function |
C4033
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: government liaison function Context triple: [Office of Management and Budget liaison functions, instanceOf, government liaison function]
-
A.
government liaison office
chosen
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
B.
government spokesperson role
A government spokesperson role is an official position responsible for communicating a government’s policies, decisions, and responses to the public and media on behalf of its leaders and institutions.
-
C.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
D.
government post
A government post is an official position or office within a governmental organization, held by an individual responsible for carrying out specific public duties and administrative functions.
-
E.
international public office
An international public office is an organizational unit within an intergovernmental or supranational body that performs administrative, regulatory, or policy functions across national boundaries in the public interest.
- F. None of above.
Provenance (1 batch)
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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.