Triple
T28285370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyan-Dombivli |
E713265
|
entity |
| Predicate | primaryRailwayStations |
P726
|
FINISHED |
| Object | Kalyan 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: Kalyan railway station | Statement: [Kalyan-Dombivli, primaryRailwayStations, Kalyan railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailwayStations Context triple: [Kalyan-Dombivli, primaryRailwayStations, Kalyan railway station]
-
A.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
B.
railwayStationInCountry
Indicates that a railway station is located within the borders of a specified country.
-
C.
hasRailStation
chosen
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
-
E.
railStationManager
Indicates that one entity manages, operates, or is responsible for the administration of a particular railway station.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
Created at: April 27, 2026, 11:25 p.m.