Triple
T18095425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Zug |
E433070
|
entity |
| Predicate | hasTaxPolicy |
P23810
|
FINISHED |
| Object | business-friendly tax regime |
—
|
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: business-friendly tax regime | Statement: [City of Zug, hasTaxPolicy, business-friendly tax regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxPolicy Context triple: [City of Zug, hasTaxPolicy, business-friendly tax regime]
-
A.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
B.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
-
C.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
taxationMethod
chosen
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1c56848190be0b8c80b30dba6c |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.