Triple
T6200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Senator |
E124
|
entity |
| Predicate | canVoteOn |
P1084
|
FINISHED |
| Object | bills |
—
|
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: bills | Statement: [New York State Senator, canVoteOn, bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canVoteOn Context triple: [New York State Senator, canVoteOn, bills]
-
A.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
B.
hasElectoralRepresentation
Indicates that one entity is represented in an electoral body or decision-making institution by another entity (such as a representative, party, or delegation).
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
E.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
- F. None of above. chosen
Provenance (4 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a242174cd4819095f78b221e1b41f1 |
completed | Feb. 28, 2026, 1:17 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.