Triple
T30016867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaigaon–Phuentsholing border crossing |
E762618
|
entity |
| Predicate | timeZoneOnBhutaneseSide |
P169703
|
FINISHED |
| Object | Bhutan Time |
—
|
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: Bhutan Time | Statement: [Jaigaon–Phuentsholing border crossing, timeZoneOnBhutaneseSide, Bhutan Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneOnBhutaneseSide Context triple: [Jaigaon–Phuentsholing border crossing, timeZoneOnBhutaneseSide, Bhutan Time]
-
A.
timeZoneSideNepal
Indicates that one entity is located on the Nepal side of a time zone boundary or offset distinction.
-
B.
timeZoneOnKoreanSide
Indicates that the referenced time zone is the one used on the Korean side of a border, division, or demarcation line.
-
C.
timeZoneSideIndia
Indicates that something is located on, associated with, or aligned to the India side of a time zone boundary or division.
-
D.
timeZoneOnAfghanSide
Indicates that the referenced time zone is the one used on the Afghan side of a border or boundary.
-
E.
timeZoneOnChineseSide
Indicates that the referenced time zone is the one used on the Chinese side of a border, boundary, or cross-border context.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 6:46 p.m.