Triple
T13803498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryde Pier Head railway station |
E331698
|
entity |
| Predicate | isEndOnJunctionFor |
P64784
|
FINISHED |
| Object | Island Line services |
—
|
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: Island Line services | Statement: [Ryde Pier Head railway station, isEndOnJunctionFor, Island Line services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndOnJunctionFor Context triple: [Ryde Pier Head railway station, isEndOnJunctionFor, Island Line services]
-
A.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
B.
isMajorJunctionOnLine
Indicates that a location serves as a primary connecting junction along a particular line or route.
-
C.
isJunctionOnLine
chosen
Indicates that a particular junction lies on, or is part of, a specified line.
-
D.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
E.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026c36108190a7436034a730a261 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.