Triple

T250899
Position Surface form Disambiguated ID Type / Status
Subject Texas legislative districts E5143 entity
Predicate hasVoters P6119 FINISHED
Object registered voters in Texas 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: registered voters in Texas | Statement: [Texas legislative districts, hasVoters, registered voters in Texas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVoters
Context triple: [Texas legislative districts, hasVoters, registered voters in Texas]
  • A. hasVotingMembers
    Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
  • B. eligibleVoters chosen
    Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
  • C. voteCountedIn
    Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
  • D. canVoteOn
    Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
  • E. hasElectedMembers
    Indicates that an entity possesses members who have attained their positions through an election 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_69a257c4bf688190a46ebbf411ab7473 completed Feb. 28, 2026, 2:49 a.m.
NER Named-entity recognition batch_69a25d38aba8819081d0958eb60ce27e completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b665f8c8190aac6fcbba2a0eebb completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:54 a.m.