Triple
T8910958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Terminals |
E212179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collective name for railway stations |
C20094
|
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: collective name for railway stations Context triple: [London Terminals, instanceOf, collective name for railway stations]
-
A.
group of passenger rail terminals
chosen
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
-
B.
railway station classification
Railway station classification is the conceptual categorization of railway stations based on attributes such as size, passenger volume, services offered, and operational importance within a rail network.
-
C.
group of light rail stations
A group of light rail stations is a collection of geographically or operationally related stops along a light rail transit line or network, treated as a single unit for planning, analysis, or management purposes.
-
D.
fictional railway station pair
A fictional railway station pair is a conceptual grouping of two imagined train stations whose locations, services, or narrative roles are defined in relation to each other within a story, game, or model world.
-
E.
train station
A train station is a designated facility where trains regularly stop to pick up and drop off passengers and sometimes freight, typically featuring platforms, ticketing services, and waiting areas.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:55 p.m.