Triple
T26979316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Standard Time (no DST) |
E679551
|
entity |
| Predicate | isSameClockTimeAs |
P8570
|
FINISHED |
| Object | Pacific Daylight 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: Pacific Daylight Time | Statement: [Mountain Standard Time (no DST), isSameClockTimeAs, Pacific Daylight Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSameClockTimeAs Context triple: [Mountain Standard Time (no DST), isSameClockTimeAs, Pacific Daylight Time]
-
A.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
-
B.
sameUTCOffsetAs
chosen
Indicates that two time-related entities share the same offset from Coordinated Universal Time (UTC), regardless of their specific time zones or locations.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62155628081908c4189b988951ad6 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:44 a.m.