Triple
T16169374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauderdale, Berwickshire and Midlothian |
E392392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic territorial designation |
C12509
|
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 territorial designation Context triple: [Lauderdale, Berwickshire and Midlothian, instanceOf, historic territorial designation]
-
A.
territorial designation
A territorial designation is a formal label or title that identifies and defines a specific geographic area or jurisdiction for political, administrative, or legal purposes.
-
B.
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.
-
C.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
D.
historical geographic entity
chosen
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
E.
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.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.