Triple

T37116058
Position Surface form Disambiguated ID Type / Status
Subject Nerul–Belapur–Panvel corridor trains E919119 entity
Predicate hasMajorStop P30882 FINISHED
Object CBD Belapur railway station E919112 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: CBD Belapur railway station | Statement: [Nerul–Belapur–Panvel corridor trains, hasMajorStop, CBD Belapur railway station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorStop
Context triple: [Nerul–Belapur–Panvel corridor trains, hasMajorStop, CBD Belapur railway station]
  • A. isMajorStopBetween
    Indicates that a location serves as a primary or significant stop along the route between two other points.
  • B. hasStops
    Indicates that a route, service, or journey includes one or more intermediate stopping points at specified locations.
  • C. majorStop
    Indicates that a location functions as a primary or significant stop along a route or service path, typically where vehicles regularly halt for boarding, alighting, or key operations.
  • D. isMajorStopForTourists
    Indicates that a location is a primary or frequently visited destination for tourists.
  • E. isMajorStationOn chosen
    Indicates that a station serves as a primary or significant stop on a particular route or line.
  • 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_69f76e9c57148190ba789dd059645bb9 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a0379a4086c8190a83df5570f737e15 completed May 12, 2026, 7:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3f6a17973481908714f1f4e46779ff completed June 27, 2026, 6:13 a.m.
PD Predicate disambiguation batch_6a037049db848190a6268bf1a8a60223 completed May 12, 2026, 6:24 p.m.
Created at: May 3, 2026, 4:15 p.m.