Triple
T14207658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Verde Time |
E352139
|
entity |
| Predicate | isBehindUTCByMinutes |
P96224
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Cape Verde Time, isBehindUTCByMinutes, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBehindUTCByMinutes Context triple: [Cape Verde Time, isBehindUTCByMinutes, 60]
-
A.
isBehindUTCByHours
Indicates that one time zone or local time lags behind Coordinated Universal Time (UTC) by a specified number of hours.
-
B.
isBehindUTC
chosen
Indicates that one time zone or local time is offset to an earlier time than Coordinated Universal Time (UTC), i.e., it lags behind UTC by a specified number of hours or minutes.
-
C.
isAheadOfUTC
Indicates that a time, date, or timezone occurs at a later (positive offset) time than Coordinated Universal Time (UTC).
-
D.
isBehindPacificTimeByHours
Indicates that one time value or time zone occurs a specified number of hours earlier than Pacific Time.
-
E.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f84f288190877116330bd54393 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:05 a.m.