Triple
T33470006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic county of Renfrewshire |
E857161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Scottish county |
C5867
|
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: traditional Scottish county Context triple: [historic county of Renfrewshire, instanceOf, traditional Scottish county]
-
A.
historic county of Scotland
chosen
A historic county of Scotland is a traditional territorial division that once served as an administrative and cultural unit, often retaining significance for identity, geography, and historical reference despite no longer having formal governmental functions.
-
B.
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.
-
C.
Scottish tradition
Scottish tradition encompasses the customs, rituals, arts, and social practices rooted in Scotland’s history and cultural heritage, including music, dance, storytelling, festivals, and clan-based identities.
-
D.
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.
-
E.
Lowland Scottish clan
A Lowland Scottish clan is a kinship-based social group from the Lowlands of Scotland, historically organized around a shared surname, territory, and leadership, but generally more feudal and less Gaelic in culture than Highland clans.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.