Triple
T17690368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FKST |
E441007
|
entity |
| Predicate | timeRelationToStandardTime |
P712
|
FINISHED |
| Object | one hour ahead |
—
|
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: one hour ahead | Statement: [FKST, timeRelationToStandardTime, one hour ahead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeRelationToStandardTime Context triple: [FKST, timeRelationToStandardTime, one hour ahead]
-
A.
relatedTimeStandard
Indicates that one time-related entity is defined, interpreted, or aligned according to a particular time standard or reference timescale.
-
B.
UTCOffsetStandardTime
chosen
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
C.
observedAsStandardTimeIn
Indicates that a particular time standard is used as the official or standard time within a specified place or region.
-
D.
timeDifferenceFromCentralStandard
Indicates the time offset between a given time reference and Central Standard Time (CST), typically expressed as the difference in hours or minutes.
-
E.
relationToUTC
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.