Triple
T12883353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Parliament elections |
E308158
|
entity |
| Predicate | regionalMSPsElected |
P107433
|
FINISHED |
| Object | 56 |
—
|
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: 56 | Statement: [Scottish Parliament elections, regionalMSPsElected, 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalMSPsElected Context triple: [Scottish Parliament elections, regionalMSPsElected, 56]
-
A.
hasConstituencyMSPs
Indicates that a political body or region is represented by specific Members of the Scottish Parliament (MSPs) elected from constituencies.
-
B.
scottishParliamentConstituency
Indicates that an entity is a constituency represented in the Scottish Parliament.
-
C.
SNPSeatsAfterElection
Indicates the number of parliamentary seats held by the SNP following a specific election.
-
D.
hasNumberOfMSPs
Indicates the relationship specifying how many managed service providers (MSPs) are associated with or involved in a given entity or context.
-
E.
mapsToScottishParliamentRegion
Indicates that one entity is assigned or corresponds to a specific Scottish Parliament electoral region.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d97c7d0598819080cab0a2314bc106 |
completed | April 10, 2026, 10:41 p.m. |
Created at: April 9, 2026, 5:39 p.m.