Triple
T26877674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justiciar of Scotia |
E676798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Scottish office |
C24745
|
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: medieval Scottish office Context triple: [Justiciar of Scotia, instanceOf, medieval Scottish office]
-
A.
medieval public office
chosen
A medieval public office is an institutional role within the governance structures of the Middle Ages, endowed with specific legal authority, duties, and privileges to administer justice, manage resources, or represent sovereign power on behalf of a ruler or community.
-
B.
Scottish hereditary office
A Scottish hereditary office is a formal position within Scotland’s historical or legal framework that is passed down through generations of a family, often carrying ceremonial, administrative, or feudal responsibilities.
-
C.
High Steward of Scotland
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.
-
D.
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.
-
E.
medieval Scottish bishopric
A medieval Scottish bishopric was an ecclesiastical jurisdiction headed by a bishop, overseeing the spiritual, administrative, and often political affairs of the Church within a defined region of Scotland 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:36 a.m.