Triple

T24769999
Position Surface form Disambiguated ID Type / Status
Subject Rochester City Council Ward 3 Representative E619694 entity
Predicate mayVoteOn P1084 FINISHED
Object city ordinances and resolutions 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: city ordinances and resolutions | Statement: [Rochester City Council Ward 3 Representative, mayVoteOn, city ordinances and resolutions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayVoteOn
Context triple: [Rochester City Council Ward 3 Representative, mayVoteOn, city ordinances and resolutions]
  • A. canVoteOn chosen
    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.
  • B. canVoteIn
    Indicates that one entity has the legal right or eligibility to participate as a voter in an election or decision-making process associated with another entity.
  • C. votingIs
    Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
  • D. mayHaveCastingVote
    Indicates that an entity is permitted to exercise a casting (tie-breaking) vote in a decision-making process.
  • E. voteFor
    Indicates that one entity casts or expresses a vote in favor of another entity or option.
  • 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_69e2fabd04488190a2d13c97be745a2d completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f410a9d0108190aab27514de6f515f completed May 1, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f40ef612c88190ab2f3f08d4a92018 completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 4:29 a.m.