Triple
T30016776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | majorIndianBorderTownForBhutanTrade |
P85285
|
FINISHED |
| Object | Jaigaon |
—
|
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: Jaigaon | Statement: [India–Bhutan relations, majorIndianBorderTownForBhutanTrade, Jaigaon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorIndianBorderTownForBhutanTrade Context triple: [India–Bhutan relations, majorIndianBorderTownForBhutanTrade, Jaigaon]
-
A.
hasBorderTownOnIndianSide
chosen
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
hasBorderTownOnNepaliSide
Indicates that a location has a corresponding town situated on the Nepali side of an international border.
-
C.
IndiaAndBhutanShare
Indicates that India and Bhutan have something in common or jointly possess, such as a shared resource, boundary, agreement, or characteristic.
-
D.
BhutanEmbassyLocationInIndia
Indicates the location(s) within India where Bhutan’s embassy or official diplomatic mission is situated.
-
E.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 29, 2026, 6:46 p.m.