Triple
T31695828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARTM A |
E808914
|
entity |
| Predicate | tariffZoneCodeType |
P70926
|
FINISHED |
| Object | alphabetic zone code |
—
|
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: alphabetic zone code | Statement: [ARTM A, tariffZoneCodeType, alphabetic zone code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tariffZoneCodeType Context triple: [ARTM A, tariffZoneCodeType, alphabetic zone code]
-
A.
tariffAssociation
Indicates a relationship where one entity is subject to, governed by, or linked through a specific tariff or set of tariff rules.
-
B.
hasTariffZoneSystem
chosen
Indicates that an entity uses or is governed by a defined tariff zone system for determining prices, fees, or charges.
-
C.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
D.
territoryCode
Indicates the standardized code assigned to a specific geographic or administrative territory in the relationship.
-
E.
tariffStructure
Indicates the specific schedule, rates, and rules that define how tariffs or fees are applied within a pricing or taxation system.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:10 p.m.