Triple
T15342061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBR welfare analysis team |
E366817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unit within public body |
C6551
|
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: unit within public body Context triple: [OBR welfare analysis team, instanceOf, unit within public body]
-
A.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
B.
internal administrative body
chosen
An internal administrative body is an organized group within an institution responsible for managing, coordinating, and overseeing its internal operations, policies, and support functions.
-
C.
non-departmental public body
A non-departmental public body is an organization that operates at arm’s length from government departments to carry out public functions, often with its own board and a degree of operational independence while remaining publicly accountable.
-
D.
office within a government department
An office within a government department is an organizational unit responsible for carrying out specific administrative, regulatory, or programmatic functions under the department’s authority.
-
E.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic area.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:17 a.m.