Triple

T35136780
Position Surface form Disambiguated ID Type / Status
Subject Sunauli border crossing E1014593 entity
Predicate borderSecurityAgencyIndia P200561 FINISHED
Object Sashastra Seema Bal 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: Sashastra Seema Bal | Statement: [Sunauli border crossing, borderSecurityAgencyIndia, Sashastra Seema Bal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderSecurityAgencyIndia
Context triple: [Sunauli border crossing, borderSecurityAgencyIndia, Sashastra Seema Bal]
  • A. borderSecurityAgencySouthAfrica
    Indicates a relationship where an agency is responsible for managing or enforcing border security in South Africa.
  • B. borderGuardDuty
    Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
  • C. hasBorderTownOnIndianSide
    Indicates that a location has a corresponding town situated on the Indian side of an international border.
  • D. borderingIndianStates
    Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
  • E. borderStation
    Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
  • F. None of above. chosen

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_69f76dd9c1848190af70d4882a2c1ad7 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff965f9be48190b015b788207be676 completed May 9, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69ff95d3015c8190b9d293fe31b859c3 completed May 9, 2026, 8:15 p.m.
PDg Predicate description generation batch_69ff965eef90819097499d1f0542378c completed May 9, 2026, 8:17 p.m.
Created at: May 3, 2026, 4:02 p.m.