Triple
T7701391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon–Turin rail axis |
E174504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed rail project |
C3405
|
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: high-speed rail project Context triple: [Lyon–Turin rail axis, instanceOf, high-speed rail project]
-
A.
proposed high-speed ground transportation system
chosen
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.
-
B.
passenger rail service
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.
-
C.
railway modernisation project
A railway modernisation project is an initiative that upgrades existing rail infrastructure, technology, and operations to improve capacity, safety, efficiency, and passenger experience.
-
D.
light rail expansion project
A light rail expansion project is a coordinated planning, design, and construction effort to extend an existing light rail transit system’s routes, capacity, and supporting infrastructure to serve additional areas and riders.
-
E.
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.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:03 p.m.