Triple
T11089050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Glasgow City Council election |
E262200
|
entity |
| Predicate | resultingControlOfCouncil |
P50144
|
FINISHED |
| Object | no overall control |
—
|
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: no overall control | Statement: [2017 Glasgow City Council election, resultingControlOfCouncil, no overall control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultingControlOfCouncil Context triple: [2017 Glasgow City Council election, resultingControlOfCouncil, no overall control]
-
A.
councilOutcome
chosen
Indicates the result or decision produced by a council after its deliberation or proceedings.
-
B.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
C.
councilPresidedOverBy
Indicates that a council or formal assembly is led, directed, or overseen by a particular person or authority.
-
D.
councilType
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
E.
viewOfCouncils
Indicates that one entity holds a particular perspective, opinion, or stance regarding councils or council-related matters.
- 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_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. |
Created at: April 8, 2026, 9:27 p.m.