Triple
T34523068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passenger Transport Executive |
E886328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statutory public body |
C3213
|
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: statutory public body Context triple: [Passenger Transport Executive, instanceOf, statutory public body]
-
A.
statutory traditional authority body
A statutory traditional authority body is a legally recognized institution that formalizes and regulates the roles, powers, and functions of traditional leaders within a state’s governance framework.
-
B.
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.
-
C.
non-governmental public body
A non-governmental public body is an organization that, while independent of direct government control, performs functions or provides services of public interest, often operating under public law or with public funding and oversight.
-
D.
public administration body
chosen
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.
-
E.
nationalized body
A nationalized body is an organization or enterprise that has been taken into public ownership and control by a national government, typically to manage services or industries deemed of strategic or 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.