Triple
T7166170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakka Qila |
E167073
|
entity |
| Predicate | locatedInTimeZone |
P109
|
FINISHED |
| Object | Asia/Karachi |
E34584
|
NE 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: Asia/Karachi | Statement: [Pakka Qila, locatedInTimeZone, Asia/Karachi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Karachi Context triple: [Pakka Qila, locatedInTimeZone, Asia/Karachi]
-
A.
Pakistan Standard Time
chosen
Pakistan Standard Time is the time zone used throughout Pakistan, corresponding to UTC+5 hours.
-
B.
Afghanistan Time
Afghanistan Time is the standard time zone used throughout Afghanistan, set at UTC+4:30.
-
C.
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.
-
D.
Asia/Aqtobe
Asia/Aqtobe is a time zone used in western Kazakhstan, centered around the city of Aktobe.
-
E.
Asia/Ust-Nera
Asia/Ust-Nera is an IANA time zone identifier used for the Ust-Nera region in Russia’s Sakha Republic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85a07388190a07054ef12870fa1 |
completed | March 27, 2026, 8:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adced6b48190bcae9af88f640584 |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:48 p.m.