Triple
T3674731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightline |
E77963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher-speed rail service |
C75
|
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: higher-speed rail service Context triple: [Brightline, instanceOf, higher-speed rail service]
-
A.
passenger rail service
chosen
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
B.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
-
C.
proposed high-speed ground transportation system
A proposed high-speed ground transportation system is a conceptual network of advanced vehicles, infrastructure, and control technologies designed to move passengers or freight rapidly and efficiently between destinations along dedicated terrestrial corridors.
-
D.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
E.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.