Triple
T666447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Standard Time |
E12872
|
entity |
| Predicate | typicalRelationToUTC |
P9276
|
FINISHED |
| Object | 12 hours ahead of UTC |
—
|
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: 12 hours ahead of UTC | Statement: [New Zealand Standard Time, typicalRelationToUTC, 12 hours ahead of UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRelationToUTC Context triple: [New Zealand Standard Time, typicalRelationToUTC, 12 hours ahead of UTC]
-
A.
relationToUTC
chosen
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
B.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
C.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
D.
relativeToEasternTime
Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
-
E.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd4f4988190a0973ceb7329b4c9 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.