Triple
T18501114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libero fare network |
E452066
|
entity |
| Predicate | usesTariffPrinciple |
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: [Libero fare network, usesTariffPrinciple, zone-based tariff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTariffPrinciple Context triple: [Libero fare network, usesTariffPrinciple, zone-based tariff]
-
A.
usesTariffSystem
chosen
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
B.
typeOfTariffPreference
Indicates the specific category or kind of tariff preference applied within a trade or customs context.
-
C.
tariffStructure
Indicates the specific schedule, rates, and rules that define how tariffs or fees are applied within a pricing or taxation system.
-
D.
legalStatusOfTariffProvisions
Indicates the legal validity, enforceability, or standing of specific tariff provisions within a regulatory or contractual framework.
-
E.
numberOfTariffConcessions
Indicates the quantity of tariff concessions that apply within a given trade or customs 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c43de48190b49b87c1bb591016 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.