Triple
T26912497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Standard Time (no DST, Arizona) |
E677426
|
entity |
| Predicate | usesStandardTimeYearRound |
P53642
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mountain Standard Time (no DST, Arizona), usesStandardTimeYearRound, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandardTimeYearRound Context triple: [Mountain Standard Time (no DST, Arizona), usesStandardTimeYearRound, yes]
-
A.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
B.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
C.
standardTimeAllYear
chosen
Indicates that a location or entity observes standard time throughout the entire year without switching to daylight saving time.
-
D.
isStandardTimeIn
Indicates that a specified time value is expressed in the standard (non-daylight-saving) time for a given region or timezone.
-
E.
observedAsStandardTimeIn
Indicates that a particular time standard is used as the official or standard time within a specified place or region.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 6:02 a.m.