Triple
T289130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shropshire Council |
E5950
|
entity |
| Predicate | usesVotingSystem |
P539
|
FINISHED |
| Object | first-past-the-post |
—
|
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: first-past-the-post | Statement: [Shropshire Council, usesVotingSystem, first-past-the-post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVotingSystem Context triple: [Shropshire Council, usesVotingSystem, first-past-the-post]
-
A.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
B.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
C.
electionMethod
chosen
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
canVoteOn
Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7c1448819082064f474633acd5 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.