Triple
T24993237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipalities of Zacatecas |
E625500
|
entity |
| Predicate | haveElectionsEvery |
P22629
|
FINISHED |
| Object | three years |
—
|
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: three years | Statement: [Municipalities of Zacatecas, haveElectionsEvery, three years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveElectionsEvery Context triple: [Municipalities of Zacatecas, haveElectionsEvery, three years]
-
A.
hasRegularElections
chosen
Indicates that a governing body or political entity holds elections at consistent, scheduled intervals according to established rules or norms.
-
B.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
C.
hasGeneralElections
Indicates that general elections are held or occur in relation to the specified entity.
-
D.
isElectedEvery
Indicates that an entity is chosen for a role or position through an election process at every specified interval or in every relevant instance.
-
E.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:04 a.m.