Triple
T10186523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Executive of London Ambulance Service NHS Trust |
E236924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector leadership position |
C7910
|
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: public sector leadership position Context triple: [Chief Executive of London Ambulance Service NHS Trust, instanceOf, public sector leadership position]
-
A.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
B.
leadership role
A leadership role is a position in which an individual is responsible for guiding, influencing, and coordinating others to achieve shared goals and outcomes.
-
C.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
-
D.
public administration position
chosen
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
E.
occupation authority leadership
A person or entity that holds a position of recognized power within an occupation, directing others and making decisions that guide the work and goals of the organization or professional domain.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:12 p.m.