Triple
T34531041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific/Efate |
E886535
|
entity |
| Predicate | previousDSTOffsetFromUTC |
P199467
|
FINISHED |
| Object | +12:00 |
—
|
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:00 | Statement: [Pacific/Efate, previousDSTOffsetFromUTC, +12:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousDSTOffsetFromUTC Context triple: [Pacific/Efate, previousDSTOffsetFromUTC, +12:00]
-
A.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
B.
DSTIsAheadOfUTC
Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
-
C.
offsetDSTApprox
Indicates an approximate time offset between entities that accounts for daylight saving time adjustments.
-
D.
previouslyObservedDST
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
-
E.
offsetFromUTCDST
Indicates that the time value is offset from Coordinated Universal Time (UTC) by a specified amount that applies during daylight saving 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: May 1, 2026, 2:02 a.m.