Triple
T22070295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copeland Borough Council |
E545387
|
entity |
| Predicate | electionsHeldEvery |
P43028
|
FINISHED |
| Object | four 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: four years | Statement: [Copeland Borough Council, electionsHeldEvery, four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionsHeldEvery Context triple: [Copeland Borough Council, electionsHeldEvery, four years]
-
A.
assemblyElectionsHeldEvery
chosen
Indicates that legislative assembly elections are conducted at a regular interval specified by the associated value.
-
B.
numberOfElectionsHeld
Indicates the total count of elections that have been conducted for a given entity or context.
-
C.
electionsHeldOn
Indicates that one or more elections took place on a specified date or set of dates.
-
D.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
E.
houseElectionsHeld
Indicates that elections have been conducted to choose members of a legislative house or lower chamber.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128881af481909b28cda2d343f4e3 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.