Triple
T18341511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Lumsden |
E439414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lord Provost of Glasgow |
C12366
|
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: Lord Provost of Glasgow Context triple: [James Lumsden, instanceOf, Lord Provost of Glasgow]
-
A.
Lord Mayor
The Lord Mayor is the ceremonial head and often the public representative of a major city’s municipal government, typically presiding over civic functions and promoting the city’s interests.
-
B.
London alderman
A London alderman is a senior elected official of the City of London Corporation who represents a ward, participates in civic governance, and helps oversee the administration and ceremonial functions of the historic financial district.
-
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 public office
chosen
A Scottish public office is an official position within Scotland's governmental or public sector institutions, held by an individual entrusted with statutory, administrative, or representative duties on behalf of the public.
-
E.
Scottish minister
A Scottish minister is a clergy member, typically of the Church of Scotland or another Scottish denomination, responsible for leading worship, preaching, administering sacraments, and providing spiritual and pastoral care within a Scottish congregation or parish.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:37 a.m.