Triple
T16412776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkestone West railway station |
E398605
|
entity |
| Predicate | primaryRailDirection |
P120426
|
FINISHED |
| Object | towards London |
—
|
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: towards London | Statement: [Folkestone West railway station, primaryRailDirection, towards London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailDirection Context triple: [Folkestone West railway station, primaryRailDirection, towards London]
-
A.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
railwayRouteDirection
chosen
Indicates the direction or orientation in which a railway route runs or is intended to be traveled.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32875bad08190bc3e2218df8c1b07 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.