Triple
T10497936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Neots railway station |
E247587
|
entity |
| Predicate | hasDepartureBoards |
P69511
|
FINISHED |
| Object | digital |
—
|
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: digital | Statement: [St Neots railway station, hasDepartureBoards, digital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartureBoards Context triple: [St Neots railway station, hasDepartureBoards, digital]
-
A.
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.
-
B.
hasDepartureScreens
chosen
Indicates that a location or facility is equipped with screens displaying departure information for services such as trains, buses, or flights.
-
C.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
-
D.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
E.
hasRailPlatforms
Indicates that an entity is equipped with one or more rail platforms used for boarding or alighting from trains.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.