Triple
T14868220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich municipal elections |
E349672
|
entity |
| Predicate | languageOfBallotsIncludes |
P9260
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Zurich municipal elections, languageOfBallotsIncludes, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfBallotsIncludes Context triple: [Zurich municipal elections, languageOfBallotsIncludes, German]
-
A.
languageOfBallots
chosen
Indicates the language or languages in which ballots are written or presented.
-
B.
languageOfOfficialLists
Indicates the language in which official lists, records, or registries are formally maintained or published.
-
C.
languageOfCampaigning
Indicates the language used to conduct or communicate a campaign (e.g., political, marketing, or advocacy efforts).
-
D.
languageOfLegislature
Indicates the language or languages officially used by a legislature to conduct its proceedings, draft laws, and perform its formal functions.
-
E.
officialLanguageOfNomination
Indicates the language officially used in the nomination process or documentation for a given entity.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5776b848190bfe3a06ff261dc31 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.