Triple
T35136782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunauli border crossing |
E1014593
|
entity |
| Predicate | timeZoneNepalSide |
P167493
|
FINISHED |
| Object | Nepal 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: Nepal Time | Statement: [Sunauli border crossing, timeZoneNepalSide, Nepal Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneNepalSide Context triple: [Sunauli border crossing, timeZoneNepalSide, Nepal Time]
-
A.
timeZoneSideNepal
chosen
Indicates that one entity is located on the Nepal side of a time zone boundary or offset distinction.
-
B.
timeZoneOnBhutaneseSide
Indicates that the referenced time zone applies specifically to the Bhutanese side of a border or boundary.
-
C.
differenceFromNepalTime
Indicates the time offset or deviation of a given time from the standard time observed in Nepal.
-
D.
timeZoneSideIndia
Indicates that something is located on, associated with, or aligned to the India side of a time zone boundary or division.
-
E.
timeZonePakistanSide
Indicates that something is located in, follows, or is associated with the time zone used on the Pakistan side of a border or region.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.