Triple
T14613399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Assembly constituencies |
E343014
|
entity |
| Predicate | hasVotingSystemType |
P94632
|
FINISHED |
| Object | plurality voting |
—
|
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: plurality voting | Statement: [London Assembly constituencies, hasVotingSystemType, plurality voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingSystemType Context triple: [London Assembly constituencies, hasVotingSystemType, plurality voting]
-
A.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
B.
hasBallotType
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
C.
typeOfVoting
chosen
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
D.
hasTypeOfVoters
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
-
E.
hasVotingPlatform
Indicates that an entity is associated with or utilizes a particular platform or system for conducting voting or elections.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.