Triple
T910786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Party of New York |
E19651
|
entity |
| Predicate | voterBase |
P3251
|
FINISHED |
| Object | independent voters in New York |
—
|
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: independent voters in New York | Statement: [Independence Party of New York, voterBase, independent voters in New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voterBase Context triple: [Independence Party of New York, voterBase, independent voters in New York]
-
A.
electoralBase
chosen
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
-
B.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
C.
voterFunction
Indicates a relationship where an entity serves in the role or capacity of a voter within a decision-making or electoral process.
-
D.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
E.
eligibleVoters
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.