Triple
T6031899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling (UK Parliament constituency) |
E134322
|
entity |
| Predicate | electsHowManyMPs |
P31812
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Stirling (UK Parliament constituency), electsHowManyMPs, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electsHowManyMPs Context triple: [Stirling (UK Parliament constituency), electsHowManyMPs, 1]
-
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.
numberOfMandates
Indicates the total count of mandates, terms, or official assignments associated with an entity in a given context.
-
C.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
D.
numberOfRepresentatives
Indicates the quantity of representatives associated with a given entity or unit.
-
E.
eachDistrictElects
Indicates that every electoral district selects or chooses its own representative or set of representatives.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056af89e881909652957f94317684 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.