Triple
T7783327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zug |
E187177
|
entity |
| Predicate | cantonTaxPolicy |
P78980
|
FINISHED |
| Object | one of the lowest tax burdens in Switzerland |
—
|
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: one of the lowest tax burdens in Switzerland | Statement: [Zug, cantonTaxPolicy, one of the lowest tax burdens in Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cantonTaxPolicy Context triple: [Zug, cantonTaxPolicy, one of the lowest tax burdens in Switzerland]
-
A.
canton
Indicates that an entity is administratively located within, belongs to, or is governed as part of a specific canton.
-
B.
cantonRepresents
Indicates that a canton serves as the official representative or governing authority for a given entity (such as a region, population, or institution).
-
C.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
D.
cantonCode
Indicates the specific administrative canton identifier associated with an entity or location.
-
E.
includesCanton
Indicates that a larger administrative or geographic entity contains or encompasses a specific canton within its boundaries.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:22 p.m.