Triple
T12883332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Parliament elections |
E308158
|
entity |
| Predicate | numberOfMSPsElected |
P31812
|
FINISHED |
| Object | 129 |
—
|
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: 129 | Statement: [Scottish Parliament elections, numberOfMSPsElected, 129]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMSPsElected Context triple: [Scottish Parliament elections, numberOfMSPsElected, 129]
-
A.
numberOfElectedMembers
chosen
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
-
B.
hasNumberOfMSPs
Indicates the relationship specifying how many managed service providers (MSPs) are associated with or involved in a given entity or context.
-
C.
numberOfMandates
Indicates the total count of mandates, terms, or official assignments associated with an entity in a given context.
-
D.
hasNumberOfMPs
Indicates the relationship that specifies how many members of parliament (MPs) are associated with a given entity.
-
E.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
- 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_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. |
Created at: April 9, 2026, 5:39 p.m.