Triple
T10883691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Time |
E256985
|
entity |
| Predicate | isBehindPacificTimeByHours |
P96225
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Alaska Time, isBehindPacificTimeByHours, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBehindPacificTimeByHours Context triple: [Alaska Time, isBehindPacificTimeByHours, 1]
-
A.
isBehindUTCByHours
Indicates that one time zone or local time lags behind Coordinated Universal Time (UTC) by a specified number of hours.
-
B.
isFourHoursBehind
Indicates that one entity’s time zone or local time is exactly four hours earlier than another reference time or time zone.
-
C.
isOneHourAheadOf
Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
-
D.
isTwoHoursAheadOf
Indicates that one entity’s time zone or local time is exactly two hours later than another entity’s.
-
E.
isThreeHoursBehind
Indicates that one entity’s time zone or local time is exactly three hours earlier than another entity’s.
- F. None of above. chosen
Provenance (4 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.