Triple
T3324073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden City Association |
E69867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British organization |
C3617
|
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 organization Context triple: [Garden City Association, instanceOf, British organization]
-
A.
British organisation
chosen
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.
-
B.
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.
-
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.
government agency of the United Kingdom
A government agency of the United Kingdom is an official public body established by the UK government to carry out specific administrative, regulatory, or service-delivery functions on its behalf.
-
E.
Japanese organization
A Japanese organization is a structured group based in Japan that coordinates people and resources to achieve shared goals, typically reflecting Japanese cultural norms, business practices, and social values.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.