Triple
T33058527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic counties of Wales |
E845909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic subdivision |
C32918
|
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: historic subdivision Context triple: [Historic counties of Wales, instanceOf, historic subdivision]
-
A.
historic subdistrict
A historic subdistrict is a geographically defined area within a larger district that contains a concentration of buildings, structures, or sites recognized for their historical, architectural, or cultural significance and is subject to preservation guidelines or protections.
-
B.
historic suburb
A historic suburb is a residential area on the outskirts of a city characterized by long-established neighborhoods, preserved architecture, and cultural or historical significance.
-
C.
former subdivision
chosen
A former subdivision is an administrative or territorial unit that once existed as a distinct part of a larger entity but has since been dissolved, merged, or reorganized and no longer functions in its original capacity.
-
D.
historic township
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
E.
historic block
A historic block is a contiguous group of buildings, streets, and public spaces recognized for their architectural, cultural, or historical significance and preserved to maintain their original character.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:25 a.m.