Triple
T18018773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debt Management Report |
E431062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK government document |
C4238
|
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: UK government document Context triple: [Debt Management Report, instanceOf, UK government document]
-
A.
British government policy statement
chosen
A British government policy statement is an official, authoritative document or announcement that sets out the UK government’s intentions, principles, and planned actions on a specific public issue or area of governance.
-
B.
UK government unit
A UK government unit is an organizational entity within the United Kingdom’s system of public administration that carries out specific governmental functions, services, or policy responsibilities under the authority of a department or minister.
-
C.
UK government-commissioned review
A UK government-commissioned review is an official, time-bound investigation or study, requested by the government and typically led by an independent expert, to examine a specific policy issue and provide evidence-based recommendations.
-
D.
English government ministry
An English government ministry is a central executive department responsible for developing and implementing public policy and administering specific areas of government activity within England.
-
E.
United Kingdom government website
A United Kingdom government website is an official online platform used by UK public sector bodies to provide information, services, and resources to citizens, businesses, and visitors.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:24 a.m.