Triple
T22666001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Commission representative |
E559788
|
entity |
| Predicate | hasRightToVote |
P97579
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [European Commission representative, hasRightToVote, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightToVote Context triple: [European Commission representative, hasRightToVote, no]
-
A.
hasElectoralRight
chosen
Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
-
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.
votingAge
Indicates the minimum age at which an individual is legally permitted to vote.
-
D.
voterEligibilityCriterion
Indicates the rule or condition that determines whether an individual is allowed to vote in a given context.
-
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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781c2c808190baf6964ca1eced6f |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.