Triple
T30009294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Islands Time |
E762409
|
entity |
| Predicate | isAheadOfNewZealandStandardTimeBy |
P168352
|
FINISHED |
| Object | 22 hours |
—
|
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: 22 hours | Statement: [Cook Islands Time, isAheadOfNewZealandStandardTimeBy, 22 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAheadOfNewZealandStandardTimeBy Context triple: [Cook Islands Time, isAheadOfNewZealandStandardTimeBy, 22 hours]
-
A.
isAheadOfUTC
Indicates that a time, date, or timezone occurs at a later (positive offset) time than Coordinated Universal Time (UTC).
-
B.
hasOffsetAheadOfMainlandNewZealand
Indicates that an entity is located at a positional offset that lies ahead of (i.e., further in the reference direction than) mainland New Zealand.
-
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.
isBehindPacificTimeByHours
Indicates that one time value or time zone occurs a specified number of hours earlier than Pacific Time.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6797fb2ac819086b9a954066473c4 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:43 p.m.