Triple

T15873530
Position Surface form Disambiguated ID Type / Status
Subject Phuentsholing E384888 entity
Predicate adjacentTo P224 FINISHED
Object Jaigaon E762619 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: Jaigaon | Statement: [Phuentsholing, adjacentTo, Jaigaon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jaigaon
Context triple: [Phuentsholing, adjacentTo, Jaigaon]
  • A. Jaigaon chosen
    Jaigaon is a bustling Indian border town in West Bengal that serves as a major commercial gateway to Bhutan, directly adjoining the Bhutanese town of Phuentsholing.
  • B. Karimganj
    Karimganj is a town in the Indian state of Assam, known as a commercial and administrative center near the India–Bangladesh border.
  • C. Jangipur
    Jangipur is a town in the Murshidabad district of the Indian state of West Bengal, known for its administrative significance and proximity to the Ganges River.
  • D. Sipajhar
    Sipajhar is a town and administrative center in the Indian state of Assam, known for its role as a local hub within Darrang district.
  • E. Garhgaon
    Garhgaon was a historic city in Assam, India, that served as an important political and administrative center of the Ahom dynasty.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fc02688190b6f070882b846516 completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa94e9b548190bec74e6d9790d241 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.