Triple
T17483033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahawalpur Airport |
E425711
|
entity |
| Predicate | timeZone |
P109
|
FINISHED |
| Object | Asia/Karachi |
—
|
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: Asia/Karachi | Statement: [Bahawalpur Airport, timeZone, Asia/Karachi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Karachi Context triple: [Bahawalpur Airport, timeZone, Asia/Karachi]
-
A.
Pakistan Standard Time
chosen
Pakistan Standard Time is the time zone used throughout Pakistan, corresponding to UTC+5 hours.
-
B.
Asia/Aden
Asia/Aden is an IANA time zone identifier representing the standard time observed in Aden, Yemen, within the Asia region.
-
C.
Afghanistan Time
Afghanistan Time is the standard time zone used throughout Afghanistan, set at UTC+4:30.
-
D.
Asia/Bahrain
Asia/Bahrain is an IANA time zone identifier representing the standard time observed in the Kingdom of Bahrain in the Arabian Gulf region.
-
E.
Asia/Qatar
Asia/Qatar is the IANA time zone identifier representing the standard time observed throughout the country of Qatar in Western Asia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451c0db14819098922453131fb40a |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:48 a.m.