Triple
T1609536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Standard Time |
E34584
|
entity |
| Predicate | typicalBusinessHoursEnd |
P14959
|
FINISHED |
| Object | 17:00 PKT |
—
|
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: 17:00 PKT | Statement: [Pakistan Standard Time, typicalBusinessHoursEnd, 17:00 PKT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBusinessHoursEnd Context triple: [Pakistan Standard Time, typicalBusinessHoursEnd, 17:00 PKT]
-
A.
typicalEndHourLocal
chosen
Indicates the usual local-time clock hour at which an activity, event, or operation typically ends.
-
B.
typicalBusinessHourStartLocalTime
Indicates the local time at which a business’s normal operating hours typically begin.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
E.
tradingHoursType
Indicates the classification of an entity’s trading hours, such as whether they are regular, extended, holiday-specific, or of another defined type.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.