Triple
T4331837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred of Bucklow |
E96767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic administrative division |
C536
|
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 administrative division Context triple: [Hundred of Bucklow, instanceOf, historic administrative division]
-
A.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
B.
former administrative territorial entity
chosen
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.
-
C.
historic state
A historic state is a former political entity or government that once exercised sovereignty over a defined territory and population but has since ceased to exist in its original form.
-
D.
historic city-state
A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
-
E.
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.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:13 p.m.