Triple
T289189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrewsbury railway station |
E5951
|
entity |
| Predicate | isJunctionFor |
P1018
|
FINISHED |
| Object | routes between England and Wales |
—
|
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: routes between England and Wales | Statement: [Shrewsbury railway station, isJunctionFor, routes between England and Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJunctionFor Context triple: [Shrewsbury railway station, isJunctionFor, routes between England and Wales]
-
A.
hasJunctionWith
chosen
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
E.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4df5508190ab75115ac6b3964e |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.