Triple
T30379034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAX landside ground transportation system |
E772770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground transportation system |
C19543
|
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: ground transportation system Context triple: [LAX landside ground transportation system, instanceOf, ground transportation system]
-
A.
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.
-
B.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
C.
ground transportation link
A ground transportation link is a physical connection, such as a road, rail line, or dedicated corridor, that enables the movement of people or goods between two or more locations on land.
-
D.
ground transportation facility
chosen
A ground transportation facility is a designated location that supports the movement, transfer, and management of passengers or goods via land-based modes such as buses, trains, cars, or trucks.
-
E.
continuous transport system
A continuous transport system is a material handling arrangement that moves goods or resources in an uninterrupted flow along a fixed path using devices such as conveyors, pipelines, or automated tracks.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.