Triple
T6414398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | unireso |
E127786
|
entity |
| Predicate | usesTariffSystem |
P70522
|
FINISHED |
| Object | zone-based tariff |
—
|
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: zone-based tariff | Statement: [unireso, usesTariffSystem, zone-based tariff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTariffSystem Context triple: [unireso, usesTariffSystem, zone-based tariff]
-
A.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
-
B.
typeOfTariffPreference
Indicates the specific category or kind of tariff preference applied within a trade or customs context.
-
C.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
D.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
E.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e6bd3881909b1979de5cdf17fb |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:42 p.m.