Triple
T16083290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereditary Bearer of the Crown of Scotland |
E390164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish noble office |
C18280
|
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 noble office Context triple: [Hereditary Bearer of the Crown of Scotland, instanceOf, Scottish noble office]
-
A.
Scottish earldom
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.
Scottish ministerial office
A Scottish ministerial office is a governmental position within the Scottish Government held by a minister responsible for specific policy areas, administration, and decision-making in Scotland.
-
C.
Scottish nobleman
A Scottish nobleman is a male member of the Scottish aristocracy who holds a hereditary or granted title, land, and social status within Scotland’s traditional feudal hierarchy.
-
D.
Polish noble office
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
-
E.
High Steward of Scotland
chosen
The High Steward of Scotland was a hereditary noble office responsible for managing the royal household and estates, which evolved into the dynastic title held by the Stewart (later Stuart) family who became kings of Scotland and England.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 4:59 a.m.