Triple
T29575464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunauli–Bhairahawa crossing |
E753430
|
entity |
| Predicate | hasTimeZoneSideIndia |
P67027
|
FINISHED |
| Object | IST (UTC+5:30) |
—
|
LITERAL 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: IST (UTC+5:30) | Statement: [Sunauli–Bhairahawa crossing, hasTimeZoneSideIndia, IST (UTC+5:30)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneSideIndia Context triple: [Sunauli–Bhairahawa crossing, hasTimeZoneSideIndia, IST (UTC+5:30)]
-
A.
timeZoneSideIndia
chosen
Indicates that something is located on, associated with, or aligned to the India side of a time zone boundary or division.
-
B.
timeZoneDeJureIndia
Indicates the officially designated legal time zone that applies within the jurisdiction of India.
-
C.
timeDifferenceWithIndianStandardTime
Indicates the time difference between a given time (or time zone) and Indian Standard Time (IST), typically expressed as an offset.
-
D.
timeZoneSide1
Indicates that the first entity is associated with or located in a particular time zone.
-
E.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 6:02 p.m.