Triple
T14271470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chase Center event service |
E353795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special event transit service |
C15962
|
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: special event transit service Context triple: [Chase Center event service, instanceOf, special event transit service]
-
A.
rush-hour service
Rush-hour service is a transportation or customer service schedule that provides increased capacity or frequency during peak demand periods to accommodate higher user volumes efficiently.
-
B.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
C.
limited-stop bus service
A limited-stop bus service is a transit route that only stops at selected key locations rather than every stop, reducing travel time for longer-distance passengers.
-
D.
public transport service feature
chosen
A public transport service feature is a specific characteristic, function, or amenity of a public transportation offering that affects how passengers access, experience, and evaluate the service.
-
E.
regional bus service
A regional bus service is a public transportation system that operates scheduled bus routes connecting multiple towns or cities within a specific geographic area.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.