Triple
T34779149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedfordshire border |
E1002592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ceremonial county boundary |
C1627
|
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: ceremonial county boundary Context triple: [Bedfordshire border, instanceOf, ceremonial county boundary]
-
A.
ceremonial county
chosen
A ceremonial county is a geographic area in a country, typically in the United Kingdom, defined primarily for the purposes of lieutenancy and traditional or ceremonial functions rather than for local government administration.
-
B.
pair of ceremonial counties
A pair of ceremonial counties is a conceptual grouping of two geographically or administratively distinct ceremonial counties considered together for comparative, analytical, or organizational purposes.
-
C.
former ceremonial county
A former ceremonial county is a geographic area in a country that once held official ceremonial or administrative status, such as having a lord-lieutenant or similar representative, but no longer functions in that capacity due to boundary changes or governmental reorganization.
-
D.
boundary commission
A boundary commission is an official body established to examine, define, and recommend changes to political or administrative boundaries, often to ensure fair representation or resolve territorial disputes.
-
E.
ceremonial precinct
A ceremonial precinct is a designated, often architecturally distinct area within a settlement or sacred landscape reserved for ritual, religious, or state ceremonial activities.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.