Triple
T23311844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayuntamiento de Albacete |
E590604
|
entity |
| Predicate | electionHeldEvery |
P22629
|
FINISHED |
| Object | 4 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: 4 years | Statement: [Ayuntamiento de Albacete, electionHeldEvery, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionHeldEvery Context triple: [Ayuntamiento de Albacete, electionHeldEvery, 4 years]
-
A.
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.
-
B.
assemblyElectionsHeldEvery
Indicates that legislative assembly elections are conducted at a regular interval specified by the associated value.
-
C.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
D.
hasRegularElections
chosen
Indicates that a governing body or political entity holds elections at consistent, scheduled intervals according to established rules or norms.
-
E.
portionUpForElectionEachCycle
Indicates what fraction of the total membership or seats is contested in each election cycle.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972bd3f88190a3859ffcf2c6ab49 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.