Triple
T6179169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsom railway station |
E137894
|
entity |
| Predicate | hasDepartureScreens |
P69511
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Epsom railway station, hasDepartureScreens, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartureScreens Context triple: [Epsom railway station, hasDepartureScreens, yes]
-
A.
hasDepartureSide
Indicates the side or direction from which an entity departs or leaves a location.
-
B.
usedOnDepartureBoards
Indicates that something (such as a name, code, or label) is the form that is shown on departure boards to represent a service or destination.
-
C.
hasPlatformScreenDoors
Indicates that a transit station or platform is equipped with platform screen doors separating passengers from the tracks.
-
D.
hasPassengerTerminalDesign
Indicates a design relationship in which one entity specifies or defines the passenger terminal layout, structure, or configuration of another entity.
-
E.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
- F. None of above. chosen
Provenance (4 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dcb77948190b5385438f81bf0a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.