Triple
T7901691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDT |
E183466
|
entity |
| Predicate | timeDifferenceFromUTCInHours |
P19135
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [IDT, timeDifferenceFromUTCInHours, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDifferenceFromUTCInHours Context triple: [IDT, timeDifferenceFromUTCInHours, 3]
-
A.
offsetFromUTCInHours
Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
-
B.
timeDifferenceFromCentralStandard
Indicates the time offset between a given time reference and Central Standard Time (CST), typically expressed as the difference in hours or minutes.
-
C.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
D.
hoursAheadOfUTC
chosen
Indicates the number of hours by which a given time or timezone is offset ahead of Coordinated Universal Time (UTC).
-
E.
differenceFromUSEasternStandardTime
Indicates the time offset or deviation of something’s time setting relative to U.S. Eastern Standard 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a40a0508190864479c2c41b12cb |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.