Triple
T26763655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lancashire |
E674876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subregion of Lancashire |
C15530
|
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: subregion of Lancashire Context triple: [East Lancashire, instanceOf, subregion of Lancashire]
-
A.
sub-region of England
chosen
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.
-
B.
subdivision of the Lake District
A subdivision of the Lake District is a defined geographic or administrative section within the broader Lake District region, distinguished by its own boundaries, characteristics, and management considerations.
-
C.
area of Greater Manchester
An area of Greater Manchester is a geographically defined locality within the metropolitan county of Greater Manchester, characterized by its own distinct boundaries, land use, and community identity.
-
D.
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.
-
E.
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.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:59 a.m.