Triple
T9492223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican conservative party |
E228917
|
entity |
| Predicate | viewedSuffrage |
P17890
|
FINISHED |
| Object | restricted suffrage |
—
|
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: restricted suffrage | Statement: [Mexican conservative party, viewedSuffrage, restricted suffrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedSuffrage Context triple: [Mexican conservative party, viewedSuffrage, restricted suffrage]
-
A.
viewOnSuffrage
chosen
Indicates a stance or opinion that an entity holds regarding the right to vote (suffrage).
-
B.
suffrageIncludes
Indicates that the scope of a group’s voting rights or electoral franchise extends to and encompasses the specified category of people or entities.
-
C.
suffrage
Indicates that an entity has the right or privilege to vote in political or organizational decision-making processes.
-
D.
hadRightToElect
Indicates that an entity possessed the legal or formal authority to choose or vote for another entity in an election or selection process.
-
E.
viewOnDemocracy
Indicates a stance, opinion, or perspective that an entity holds regarding the concept or practice of democracy.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80ca26bc819084add20027aea4a5 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.