Triple
T18501100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libero fare network |
E452066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport tariff network |
C12710
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public transport tariff network Context triple: [Libero fare network, instanceOf, public transport tariff network]
-
A.
public transport pricing scheme
A public transport pricing scheme is a structured set of rules and fares that determines how passengers are charged for using public transit services based on factors such as distance, time, mode, and user category.
-
B.
fare network
chosen
A fare network is an interconnected system of transportation routes, services, and pricing structures through which passengers can travel using coordinated tickets or payment methods.
-
C.
bus service network
A bus service network is an interconnected system of bus routes, stops, schedules, and vehicles designed to transport passengers efficiently across a defined geographic area.
-
D.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
E.
transit fare product
A transit fare product is a purchasable medium (such as a ticket, pass, or stored value) that grants a rider the right to access and use public transportation services under specified conditions.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 10, 2026, 11:36 a.m.