Triple
T34975603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Douglas of Hawick and Tibbers |
E1008667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish courtesy title |
C672
|
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 courtesy title Context triple: [Lord Douglas of Hawick and Tibbers, instanceOf, Scottish courtesy title]
-
A.
Scottish judicial title
A Scottish judicial title is the formal designation adopted by a judge in Scotland, typically reflecting a territorial or honorific name used in official legal and court proceedings.
-
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.
peerage title
chosen
A peerage title is a hereditary or life rank of nobility granted by a sovereign, conferring social status and often certain legal or ceremonial privileges within a hierarchical aristocratic system.
-
D.
historic Scottish naval title
A historic Scottish naval title is an official rank or honorific once used within Scotland’s maritime forces or administration, reflecting its distinct naval traditions and governance before integration into broader British naval structures.
-
E.
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.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.