Triple
T31268207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-Welle zone 570 |
E797307
|
entity |
| Predicate | tariffNetwork |
P70926
|
FINISHED |
| Object | A-Welle |
—
|
NE NERFINISHED |
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: A-Welle | Statement: [A-Welle zone 570, tariffNetwork, A-Welle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tariffNetwork Context triple: [A-Welle zone 570, tariffNetwork, A-Welle]
-
A.
tariffStructure
Indicates the specific schedule, rates, and rules that define how tariffs or fees are applied within a pricing or taxation system.
-
B.
hasTariffZoneSystem
chosen
Indicates that an entity uses or is governed by a defined tariff zone system for determining prices, fees, or charges.
-
C.
usesTariffSystem
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
D.
legalStatusOfTariffProvisions
Indicates the legal validity, enforceability, or standing of specific tariff provisions within a regulatory or contractual framework.
-
E.
isFullyWithinTariffZone
Indicates that one entity lies entirely inside the boundaries of a specified tariff zone without extending beyond it.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.