Triple
T26099751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Building Commission |
E658364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British public body |
C27015
|
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 body Context triple: [Church Building Commission, instanceOf, British public body]
-
A.
UK public authority
chosen
A UK public authority is an organization or body in the United Kingdom that carries out public functions or services and is subject to public law duties, including transparency and accountability obligations.
-
B.
British government department
A British government department is an administrative unit of the UK government responsible for developing and implementing public policy and delivering specific services within a defined area of national governance.
-
C.
British government ministry
A British government ministry is a central department of the UK government, headed by a minister, responsible for developing and implementing public policy and administering specific areas of national governance.
-
D.
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.
-
E.
British organisation
A British organisation is an entity based in or primarily operating within the United Kingdom, formed by individuals or groups to pursue specific social, cultural, economic, or political objectives under UK legal and regulatory frameworks.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:54 p.m.