Triple
T30956263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Hone |
E788684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British public sector executive |
C4297
|
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: British public sector executive Context triple: [Dennis Hone, instanceOf, British public sector executive]
-
A.
British civil servant
chosen
A British civil servant is a non-political government employee who supports the administration and implementation of public policy within the United Kingdom’s civil service.
-
B.
British civil service position
A British civil service position is a professional role within the UK government’s permanent administrative machinery, responsible for implementing policies, delivering public services, and supporting ministers in their official duties.
-
C.
Australian Public Service employee
An Australian Public Service employee is a non-political government worker engaged under the Public Service Act to deliver programs, develop policy, and provide services on behalf of the Australian Government.
-
D.
British public figure
A British public figure is an individual from the United Kingdom who holds a prominent role or visibility in society—such as in politics, media, arts, sports, or business—and whose actions and opinions attract significant public and media attention.
-
E.
Irish civil servant
An Irish civil servant is a government employee in Ireland who works within public sector departments or agencies to implement policies, deliver public services, and support the functioning of the state in a politically neutral manner.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.