Triple
T6140159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo Award final ballot counting method |
E136940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ranked-choice voting system |
C6623
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ranked-choice voting system Context triple: [Hugo Award final ballot counting method, instanceOf, ranked-choice voting system]
-
A.
proportional system
A proportional system is a method of representation or allocation in which outcomes (such as seats, resources, or influence) are distributed in direct proportion to measured inputs like votes, shares, or contributions.
-
B.
parliamentary representation system
A parliamentary representation system is a political framework in which citizens elect representatives to a legislative body that forms or supports the government, typically reflecting party strength in proportion to votes received.
-
C.
cryptographic voting system
A cryptographic voting system is a secure, privacy-preserving election mechanism that uses cryptographic protocols to ensure ballot secrecy, voter authentication, integrity of tallies, and verifiable results without revealing individual votes.
-
D.
electoral process
chosen
The electoral process is the structured sequence of activities, rules, and institutions through which citizens select representatives or decide public issues by casting and counting votes.
-
E.
congressional district system
A congressional district system is a method of dividing a country or state into geographically defined electoral areas, each of which elects its own representative to a legislative body.
- F. None of above.
Provenance (1 batch)
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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.