Triple
T2634740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presiding Officer of the Scottish Parliament |
E59716
|
entity |
| Predicate | isNonPartisanOffice |
P5069
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Presiding Officer of the Scottish Parliament, isNonPartisanOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonPartisanOffice Context triple: [Presiding Officer of the Scottish Parliament, isNonPartisanOffice, true]
-
A.
isNonpartisanOffice
chosen
Indicates that the office or position is not affiliated with, controlled by, or contested along formal political party lines.
-
B.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
-
C.
isElectoralOffice
Indicates that the referenced position or role is an official public office filled through an electoral process.
-
D.
nonPartisan
Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
-
E.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
- F. None of above.
Provenance (3 batches)
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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e085b0819089db4103c0d8cd9b |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.