Triple
T5252294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield City Region |
E118616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combined authority area |
C6068
|
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: combined authority area Context triple: [Sheffield City Region, instanceOf, combined authority area]
-
A.
combined authority
chosen
A combined authority is a legal entity formed by two or more local government areas that collaborate to exercise shared strategic powers and responsibilities, typically over transport, economic development, and regional planning.
-
B.
combined statistical area
A combined statistical area is a U.S. geographic region consisting of adjacent metropolitan and/or micropolitan areas that have substantial economic and social integration, as measured by commuting ties.
-
C.
occupation authority component
An occupation authority component is a system element responsible for defining, managing, and enforcing rules, permissions, and responsibilities associated with specific roles or professions within an organizational or regulatory context.
-
D.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
-
E.
metropolitan authority
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.