Triple
T13024231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bermondsey Underground station |
E326258
|
entity |
| Predicate | lineDirectionTo |
P107515
|
FINISHED |
| Object | Jubilee line westbound towards Stanmore |
—
|
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: Jubilee line westbound towards Stanmore | Statement: [Bermondsey Underground station, lineDirectionTo, Jubilee line westbound towards Stanmore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineDirectionTo Context triple: [Bermondsey Underground station, lineDirectionTo, Jubilee line westbound towards Stanmore]
-
A.
lineOrientation
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
B.
lineDirectionSouth
Indicates that a line or path is oriented or directed toward the south.
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
lineExtendedTo
Indicates that one line is formed by extending another line beyond its original endpoint.
-
E.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:52 p.m.