Triple
T2774264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 109th United States Congress |
E61530
|
entity |
| Predicate | nonVotingHouseMembers |
P33030
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [109th United States Congress, nonVotingHouseMembers, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonVotingHouseMembers Context triple: [109th United States Congress, nonVotingHouseMembers, 6]
-
A.
hasNonvotingMember
Indicates that an entity is associated with a member who participates in some capacity but does not possess formal voting rights in the relevant decision-making process.
-
B.
nonVoting
chosen
Indicates that an entity participates in a group or organization without possessing the right to vote in its decisions.
-
C.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
-
D.
haveUpperHouseRepresentationIn
Indicates that an entity holds or is assigned representation in a specified upper legislative chamber.
-
E.
senateMembership
Indicates that an entity holds or has held a position as a member of a senate.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.