Triple
T28957334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salkia |
E731198
|
entity |
| Predicate | nearbyMajorStation |
P188083
|
FINISHED |
| Object | Howrah Junction railway station |
—
|
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: Howrah Junction railway station | Statement: [Salkia, nearbyMajorStation, Howrah Junction railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMajorStation Context triple: [Salkia, nearbyMajorStation, Howrah Junction railway station]
-
A.
nearbyHeritageStation
Indicates that one entity is located close to a heritage (historically or culturally significant) station.
-
B.
nearbyMajorStationNorth
Indicates that a major station is located to the north and in close proximity to the referenced entity.
-
C.
nearbyMajorStationSouth
Indicates that the referenced entity is located near a major station that lies to its south.
-
D.
nearestSuburbanRailwayStation
Indicates the relationship where a given place is associated with the suburban railway station that is geographically closest to it.
-
E.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
- F. None of above. chosen
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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 28, 2026, 8:48 a.m.