Triple
T20103408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pingshan Subdistrict (historical) |
E496605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former subdistrict |
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: former subdistrict Context triple: [Pingshan Subdistrict (historical), instanceOf, former subdistrict]
-
A.
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.
-
B.
former rural district
A former rural district is an administrative subdivision that once governed a predominantly countryside area but has since been dissolved, merged, or restructured into a different territorial unit.
-
C.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
D.
former non-metropolitan district
A former non-metropolitan district is an abolished local government district in England that once operated below county level outside major metropolitan areas, typically handling local services such as housing, planning, and waste collection.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:27 p.m.