Triple
T17918861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vauxhall Underground station |
E448010
|
entity |
| Predicate | hasNationalRailInterchange |
P98214
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Vauxhall Underground station, hasNationalRailInterchange, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalRailInterchange Context triple: [Vauxhall Underground station, hasNationalRailInterchange, yes]
-
A.
hasRailInterchangeFunction
Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
-
B.
hasNationalRailPlatforms
Indicates that an entity possesses one or more platforms used by the national rail network for train services.
-
C.
hasInterchangeStationWith
chosen
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
D.
hasNationalRailService
Indicates that a place or facility is served by a country's national rail transportation network.
-
E.
hasNationalRailCategory
Indicates that an entity is assigned a specific classification or category within a national rail system.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30844548190b7a43c2f093f35d7 |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.