Triple
T26754617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moray Firth Special Area of Conservation |
E674637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area of Scotland |
C14729
|
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: protected area of Scotland Context triple: [Moray Firth Special Area of Conservation, instanceOf, protected area of Scotland]
-
A.
Special Area of Conservation
chosen
A Special Area of Conservation is a protected site designated under the EU Habitats Directive to safeguard rare, endangered, or vulnerable natural habitats and species of European importance.
-
B.
region of Scotland
A region of Scotland is a geographically defined area within the country characterized by shared administrative boundaries, cultural identity, and physical landscape features.
-
C.
Area of Outstanding Natural Beauty
An Area of Outstanding Natural Beauty is a designated landscape in the UK protected for its distinctive natural beauty, wildlife, and cultural heritage, where conservation and public enjoyment are prioritized.
-
D.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
E.
town in Scotland
A town in Scotland is a moderately sized, historically rooted settlement that serves as a local center for housing, commerce, services, and community life within the Scottish cultural and administrative landscape.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:55 a.m.