Triple
T11089060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Glasgow City Council election |
E262200
|
entity |
| Predicate | GreenSeatChange |
P97164
|
FINISHED |
| Object | +2 |
—
|
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: +2 | Statement: [2017 Glasgow City Council election, GreenSeatChange, +2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GreenSeatChange Context triple: [2017 Glasgow City Council election, GreenSeatChange, +2]
-
A.
otherSeat
Indicates that one entity is the alternative or different seat relative to another seat in a given context.
-
B.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
C.
chairDiscretion
Indicates that something occurs, is decided, or is allowed based on the judgment or discretionary authority of the chairperson or presiding officer.
-
D.
PPSeats
Indicates that an entity provides or contains seats, typically specifying the seating capacity or arrangement associated with it.
-
E.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
- 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.