Triple
T26979319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Standard Time (no DST) |
E679551
|
entity |
| Predicate | isTwoHoursBehindOf |
P7778
|
FINISHED |
| Object | Eastern 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: Eastern Standard Time | Statement: [Mountain Standard Time (no DST), isTwoHoursBehindOf, Eastern Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTwoHoursBehindOf Context triple: [Mountain Standard Time (no DST), isTwoHoursBehindOf, Eastern Standard Time]
-
A.
isTwoHoursBehind
chosen
Indicates that one entity’s time zone or clock is exactly two hours earlier than another entity’s time zone or clock.
-
B.
isTwoHoursAheadOf
Indicates that one entity’s time zone or local time is exactly two hours later than another entity’s.
-
C.
isThreeHoursBehind
Indicates that one entity’s time zone or local time is exactly three hours earlier than another entity’s.
-
D.
isFourHoursBehind
Indicates that one entity’s time zone or local time is exactly four hours earlier than another reference time or time zone.
-
E.
isOneHourAheadOf
Indicates that one entity’s local time is exactly one hour later than the other entity’s local 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.