Triple
T30880808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tees Valley combined authority area |
E786606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub‑regional area |
C2248
|
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: sub‑regional area Context triple: [Tees Valley combined authority area, instanceOf, sub‑regional area]
-
A.
subregion of metropolitan area
A subregion of a metropolitan area is a geographically or functionally distinct part of a larger urban region, characterized by shared land use, demographics, infrastructure, or economic activity.
-
B.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
C.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
D.
autonomous area
An autonomous area is a geographically defined region that possesses a degree of self-governance and decision-making authority independent from the central governing body.
-
E.
sub-prefecture
A sub-prefecture is an administrative division below the level of a prefecture, typically overseen by a sub-prefect and responsible for local governance and implementation of national or regional policies within its territory.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.