Triple
T28431922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Norwood railway station |
E715154
|
entity |
| Predicate | servedByNightBusRoutes |
P104314
|
FINISHED |
| Object | London Buses route N2 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: London Buses route N2 | Statement: [West Norwood railway station, servedByNightBusRoutes, London Buses route N2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByNightBusRoutes Context triple: [West Norwood railway station, servedByNightBusRoutes, London Buses route N2]
-
A.
hasNightBusService
chosen
Indicates that a transportation route or stop is served by buses operating during nighttime hours.
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
servedByNationalRoute
Indicates that a location or facility is connected to and accessible via a specified national route.
-
D.
streetServedBy
Indicates that a particular street is provided with service or coverage by a specified service provider or infrastructure.
-
E.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
- F. None of above.
Provenance (3 batches)
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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 28, 2026, 1:40 a.m.