Triple
T21314721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Montgomery |
E525435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Scottish noble family |
C1545
|
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: historical Scottish noble family Context triple: [Clan Montgomery, instanceOf, historical Scottish noble family]
-
A.
Scottish noble family branch
A Scottish noble family branch is a cadet line descending from a principal aristocratic house in Scotland, holding its own titles, lands, and heraldic distinctions while remaining part of the wider clan or lineage.
-
B.
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.
-
C.
Scottish royal dynasty
A Scottish royal dynasty is a hereditary ruling family that held the throne of Scotland over successive generations, shaping the kingdom’s political, cultural, and dynastic history.
-
D.
Scottish clan
chosen
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.
-
E.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:28 p.m.