Triple
T38602793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBKF |
E934259
|
entity |
| Predicate | usesStandardTimeZone |
P132463
|
FINISHED |
| Object | Mountain Standard 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: Mountain Standard Time | Statement: [KBKF, usesStandardTimeZone, Mountain Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandardTimeZone Context triple: [KBKF, usesStandardTimeZone, Mountain Standard Time]
-
A.
hasStandardTimeZone
chosen
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
B.
hasStandardTimeUTCOffset
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
-
C.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
D.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
E.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:32 p.m.