Triple

T11089057
Position Surface form Disambiguated ID Type / Status
Subject 2017 Glasgow City Council election E262200 entity
Predicate SNPSeatChange P97163 FINISHED
Object +9 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: +9 | Statement: [2017 Glasgow City Council election, SNPSeatChange, +9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SNPSeatChange
Context triple: [2017 Glasgow City Council election, SNPSeatChange, +9]
  • A. DemocraticSeatChange
    Indicates the change in the number of seats held by the Democratic Party between two specified electoral outcomes or time points.
  • B. winningPartySeatChange
    Indicates the change in the number of seats held by the winning party compared to a previous election or reference point.
  • C. LabourSeatChange
    Indicates a change in the number of parliamentary seats held by the Labour Party between two electoral outcomes.
  • D. liberalDemocratNetSeatChange
    Indicates the change in the number of parliamentary or legislative seats held by the Liberal Democrats between two specified elections or time points.
  • E. LiberalSeatChange
    Indicates a change in the number of seats held by the Liberal party between two points in time.
  • F. None of above. chosen

Provenance (4 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799e844b08190987c7c8e8d626510 completed April 9, 2026, 12:22 p.m.
PD Predicate disambiguation batch_69d744185a5881909ba4cf151d1798ec completed April 9, 2026, 6:15 a.m.
PDg Predicate description generation batch_69d750ca52ec8190a559432a5de106fd completed April 9, 2026, 7:10 a.m.
Created at: April 8, 2026, 9:27 p.m.