Triple
T8092704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Borough of Kingston upon Thames |
E188906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government district in England |
C4328
|
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: local government district in England Context triple: [Royal Borough of Kingston upon Thames, instanceOf, local government district in England]
-
A.
town in England
A town in England is a moderately sized urban settlement that serves as a local center for housing, commerce, services, and community life, typically smaller than a city and governed by its own local authority.
-
B.
district of London
chosen
A district of London is a defined urban area within the Greater London region, characterized by its own local identity, history, and mix of residential, commercial, and cultural features.
-
C.
sub-region of England
A sub-region of England is a defined geographic and administrative area within the country that groups together multiple counties or local authorities for planning, statistical, or governance purposes.
-
D.
non-metropolitan district council
A non-metropolitan district council is a local government authority in a two-tier system in England responsible for services such as housing, local planning, waste collection, and leisure within a defined district outside major metropolitan areas.
-
E.
shire district
A shire district is a local government subdivision within a non-metropolitan county, responsible for providing certain public services and administration for its designated area.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:30 p.m.