Triple
T25006105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl's Court (Neverwhere) |
E625844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fantastical London Underground station |
C18727
|
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: fantastical London Underground station Context triple: [Earl's Court (Neverwhere), instanceOf, fantastical London Underground station]
-
A.
Overground station
An overground station is a railway or transit facility located at or above ground level where passengers board, alight, and transfer between surface-level trains or transit services.
-
B.
fictional railway station
chosen
A fictional railway station is an imagined transit hub within a narrative world, serving as a setting for travel, encounters, and events that support the story’s themes and plot.
-
C.
London Underground station entrance
A London Underground station entrance is a designated access point at street level that allows passengers to enter or exit the Tube network, typically marked by signage, stairways, escalators, or lifts leading to the station concourse and platforms.
-
D.
London Underground depot
A London Underground depot is a specialized facility where Underground trains are stored, maintained, cleaned, and prepared for daily service on the network.
-
E.
London Underground interchange
A London Underground interchange is a station or complex where passengers can transfer between two or more Underground lines (and sometimes other rail services) within a single integrated facility.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:05 a.m.