Triple
T25400269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southend Victoria |
E636398
|
entity |
| Predicate | isCommuterTerminusFor |
P58512
|
FINISHED |
| Object | London |
—
|
NE NERFINISHED |
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: London | Statement: [Southend Victoria, isCommuterTerminusFor, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommuterTerminusFor Context triple: [Southend Victoria, isCommuterTerminusFor, London]
-
A.
isKeyCommuterStation
chosen
Indicates that a station functions as a major hub for regular commuter traffic, serving as a primary access or transfer point for daily travelers.
-
B.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
C.
isPassengerStationFor
Indicates that a station serves as a boarding and alighting point for passengers on a particular transportation line or service.
-
D.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
E.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f978a881909842e36f61b9a40a |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:50 p.m.