Triple
T33601199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BART distance-based fare system |
E860724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | distance-based pricing model |
C28540
|
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: distance-based pricing model Context triple: [BART distance-based fare system, instanceOf, distance-based pricing model]
-
A.
dynamic pricing facility
A dynamic pricing facility is a system or component that automatically adjusts prices in real time based on factors such as demand, supply, customer behavior, and market conditions.
-
B.
public transport pricing scheme
chosen
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.
-
C.
price determination model
A price determination model is a conceptual framework that explains how the interaction of supply, demand, and market conditions leads to the establishment of prices for goods or services.
-
D.
road pricing scheme
A road pricing scheme is a system for charging drivers fees to use specific roads or areas, typically to manage congestion, reduce environmental impacts, or fund transportation infrastructure.
-
E.
distance function
A distance function is a rule that assigns a non-negative real number to quantify how far apart two elements are in a given space, typically satisfying properties like non-negativity, identity, symmetry, and the triangle inequality.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.