Triple
T16743125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Andrew's Society |
E406880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish heritage society |
C37857
|
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 heritage society Context triple: [St. Andrew's Society, instanceOf, Scottish heritage society]
-
A.
Scottish clan
A Scottish clan is a traditional kinship group originating in the Scottish Highlands, united by a shared surname, ancestry (real or assumed), territory, and allegiance to a hereditary chief.
-
B.
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.
-
C.
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.
-
D.
Scottish landed family
A Scottish landed family is a historically established kin group that owns or once owned significant estates in Scotland, often holding social status, local influence, and sometimes hereditary titles tied to their ancestral lands.
-
E.
historic county of Scotland
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.
- F. None of above. chosen
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.