Triple
T4294790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater London Council (in respect of residual functions) |
E99684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public authority residual body |
C14004
|
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 authority residual body Context triple: [Greater London Council (in respect of residual functions), instanceOf, public authority residual body]
-
A.
public port authority
A public port authority is a government or quasi-governmental entity responsible for developing, managing, and regulating port facilities and maritime operations within a designated jurisdiction.
-
B.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
public communication body
A public communication body is an organization or institution responsible for disseminating information, messages, or media content to the general public through various communication channels.
-
D.
body of public law
The body of public law is the collection of legal rules and principles that govern the organization, powers, and functions of the state and its relationship with individuals and other public entities.
-
E.
administrative authority
chosen
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.