Triple
T32079503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middelfart Municipality |
E819253
|
entity |
| Predicate | electsMunicipalCouncilEvery |
P197485
|
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: [Middelfart Municipality, electsMunicipalCouncilEvery, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electsMunicipalCouncilEvery Context triple: [Middelfart Municipality, electsMunicipalCouncilEvery, 4 years]
-
A.
electMunicipalCouncilBy
Indicates that a municipal council is chosen or appointed through the action or decision of a specified agent or process.
-
B.
electsCouncillorsTo
Indicates a relationship where one entity selects or chooses individuals to serve as councillors in another entity or governing body.
-
C.
hasMunicipalCouncilTerm
Indicates that a municipal council serves or holds office during a specified term or period.
-
D.
councilMaySelect
Indicates that a council has the authority or option to choose or appoint something or someone.
-
E.
includesMunicipalCouncil
Indicates that an administrative or territorial entity contains or is served by a municipal council as part of its governance structure.
- F. None of above. chosen
Provenance (4 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 1, 2026, 12:24 a.m.