Triple

T36062069
Position Surface form Disambiguated ID Type / Status
Subject Torugart Pass E1043113 entity
Predicate hasAlternativeTransborderRoute P110142 FINISHED
Object Irkeshtam Pass 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: Irkeshtam Pass | Statement: [Torugart Pass, hasAlternativeTransborderRoute, Irkeshtam Pass]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeTransborderRoute
Context triple: [Torugart Pass, hasAlternativeTransborderRoute, Irkeshtam Pass]
  • A. hasBorderCrossingsType
    Indicates that a border crossing is classified by a specific type or category of crossing (e.g., road, rail, pedestrian, maritime).
  • B. haveCrossBorderCorridor chosen
    Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
  • 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. hasBorderCrossing
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • E. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity 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_69f76e2f09448190b0486d5ecad5e243 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fdee770af48190aca2670db50f8b49 completed May 8, 2026, 2:08 p.m.
PD Predicate disambiguation batch_69fdecec98a08190a357d816dc2a6dbe completed May 8, 2026, 2:02 p.m.
Created at: May 3, 2026, 4:08 p.m.