Triple
T19012003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic county of Salop (Shropshire) |
E465251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional county of England |
C12371
|
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: traditional county of England Context triple: [historic county of Salop (Shropshire), instanceOf, traditional county of England]
-
A.
historic county of England
chosen
A historic county of England is a traditional geographic and cultural subdivision whose boundaries were established for administrative, judicial, and social purposes before modern local government reforms.
-
B.
traditional county
A traditional county is a historical administrative and geographic subdivision of a country, often predating modern local government structures and retaining cultural and identity significance despite changes in official boundaries.
-
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.
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.
-
E.
shire county
A shire county is a traditional administrative division in England, typically encompassing both rural and urban areas, governed by a county council responsible for local services such as education, transport, and social care.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.