Triple

T29884593
Position Surface form Disambiguated ID Type / Status
Subject Sikkim–Jhapa sector crossings E758974 entity
Predicate connectsAdministrativeRegion P87027 FINISHED
Object Sikkim 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: Sikkim | Statement: [Sikkim–Jhapa sector crossings, connectsAdministrativeRegion, Sikkim]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsAdministrativeRegion
Context triple: [Sikkim–Jhapa sector crossings, connectsAdministrativeRegion, Sikkim]
  • A. connectsAdministrativeArea chosen
    Indicates a relationship where one entity serves as a link or route between two administrative areas (such as regions, districts, or municipalities).
  • B. connectsProvinceOrRegion
    Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
  • C. associatedAdministrativeRegion
    Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
  • D. representsAdministrativeRegion
    Indicates that one entity serves as the administrative region or jurisdiction within which the other entity is governed or managed.
  • E. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • 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_69f2245de2f48190a481404896b56254 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fdd5fba5048190b7d430ae2054a1fd completed May 8, 2026, 12:24 p.m.
PD Predicate disambiguation batch_69fdd35f76f88190a1854ea27132f9c7 completed May 8, 2026, 12:13 p.m.
Created at: April 29, 2026, 5:59 p.m.