Triple
T22686916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 52nd United States Congress |
E560940
|
entity |
| Predicate | votingSystemForHouse |
P1307
|
FINISHED |
| Object | single-member districts |
—
|
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: single-member districts | Statement: [52nd United States Congress, votingSystemForHouse, single-member districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemForHouse Context triple: [52nd United States Congress, votingSystemForHouse, single-member districts]
-
A.
votingSystemChamber
Indicates the specific legislative chamber in which a given voting system is used or applies.
-
B.
votingSystemUpperHouse
Indicates a relationship where a specified voting system is used to elect or constitute the members of an upper legislative house.
-
C.
hasVotingSystemLowerHouse
chosen
Indicates that a political entity’s lower legislative chamber uses a specified voting or electoral system.
-
D.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
E.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178649aac8190a9d41f5d82895bdf |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.