Triple

T26892557
Position Surface form Disambiguated ID Type / Status
Subject Bangladesh Railway E677813 entity
Predicate hasBorderCrossingService P10963 FINISHED
Object India 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: India | Statement: [Bangladesh Railway, hasBorderCrossingService, India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderCrossingService
Context triple: [Bangladesh Railway, hasBorderCrossingService, India]
  • A. hasBorderCrossing
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • B. hasBorderCrossingFunction chosen
    Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
  • C. hasBorderCrossingSide
    Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
  • D. hasRailBorderCrossing
    Indicates that two places are connected by at least one official border crossing that is served by rail transport.
  • E. usesBorderCrossing
    Indicates that one entity makes use of a specific border crossing point to pass from one jurisdiction or territory to another.
  • 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_69eee9befee48190a26f214faa867be7 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6afebd7ec8190ab696f363d84abf0 completed May 3, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69f6aca204148190850a3dc325bc07b7 completed May 3, 2026, 2:02 a.m.
Created at: April 27, 2026, 5:46 a.m.