Triple
T25420209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRF |
E636959
|
entity |
| Predicate | associatedWithRailwayStationName |
P41163
|
FINISHED |
| Object | Bradford Forster Square |
E162822
|
NE 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: Bradford Forster Square | Statement: [BRF, associatedWithRailwayStationName, Bradford Forster Square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRailwayStationName Context triple: [BRF, associatedWithRailwayStationName, Bradford Forster Square]
-
A.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
B.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
C.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
-
D.
associatedWithStationName
chosen
Indicates a relationship where something is linked or connected to a particular station identified by its name.
-
E.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
- F. None of above.
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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1089977f888190b2bcdee3449432b0 |
completed | May 22, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 21, 2026, 1:56 p.m.