Triple
T424361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northesk |
E8173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish territorial designation |
C673
|
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: Scottish territorial designation Context triple: [Northesk, instanceOf, Scottish territorial designation]
-
A.
Scottish earldom
chosen
A Scottish earldom is a hereditary noble title in the peerage of Scotland, historically granting its holder territorial authority, social precedence, and certain feudal or ceremonial privileges within the Scottish realm.
-
B.
former British colony
A former British colony is a territory that was once governed or administered by the British Empire but has since gained independence or undergone a change in political status.
-
C.
Scottish given name
A Scottish given name is a personal first name traditionally used in Scotland, often derived from Gaelic, Norse, or Anglo-Saxon origins and reflecting the country’s linguistic and cultural heritage.
-
D.
overseas territory
An overseas territory is a geographically separate and often distant region that is under the sovereignty or jurisdiction of a country but not fully integrated as part of its main national territory.
-
E.
Scottish surname
A Scottish surname is a family name originating from Scotland, often derived from Gaelic, Norse, or Anglo-Norman roots and reflecting ancestral occupations, locations, or clan affiliations.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.