Triple
T22452358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsborough (district of Sheffield) |
E555025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Sheffield |
C46322
|
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: district of Sheffield Context triple: [Hillsborough (district of Sheffield), instanceOf, district of Sheffield]
-
A.
district of Sunderland
A district of Sunderland is an administrative subdivision within the City of Sunderland that encompasses specific neighborhoods or communities for local governance and service provision.
-
B.
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.
-
C.
shire district
A shire district is a local government subdivision within a non-metropolitan county, responsible for providing specific municipal services and administration for its designated area.
-
D.
district of Birmingham
A district of Birmingham is an administrative and geographic subdivision of the city, characterized by its own local identity, residential and commercial areas, and community services within the wider Birmingham metropolitan area.
-
E.
district of Bristol
A district of Bristol is a defined geographic and administrative area within the city of Bristol, characterized by its own local identity, land use, and community functions.
- F. None of above. chosen
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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.