Triple
T29598039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raxaul–Birgunj crossing |
E754358
|
entity |
| Predicate | timeZoneSideNepal |
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: [Raxaul–Birgunj crossing, timeZoneSideNepal, Nepal Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneSideNepal Context triple: [Raxaul–Birgunj crossing, timeZoneSideNepal, Nepal Time]
-
A.
differenceFromNepalTime
Indicates the time offset or deviation of a given time from the standard time observed in Nepal.
-
B.
timeZoneSideIndia
Indicates that something is located on, associated with, or aligned to the India side of a time zone boundary or division.
-
C.
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.
-
D.
timeZoneOnAfghanSide
Indicates that the referenced time zone is the one used on the Afghan side of a border or boundary.
-
E.
timeZoneOnKoreanSide
Indicates that the referenced time zone is the one used on the Korean side of a border, division, or demarcation line.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66db95ed481908ec804df6d8b50a3 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:19 p.m.