Triple
T26160238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham Daylight Time |
E660087
|
entity |
| Predicate | DSTRelativeToNZSTInMinutes |
P18250
|
FINISHED |
| Object | +105 |
—
|
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: +105 | Statement: [Chatham Daylight Time, DSTRelativeToNZSTInMinutes, +105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTRelativeToNZSTInMinutes Context triple: [Chatham Daylight Time, DSTRelativeToNZSTInMinutes, +105]
-
A.
DSTRelativeToChathamStandardTimeInMinutes
Indicates the number of minutes by which a time is offset from Chatham Standard Time due to daylight saving time.
-
B.
offsetFromNewZealandStandardTime
chosen
Indicates the time difference between a given time reference and New Zealand Standard Time (NZST).
-
C.
relationToUTC
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
D.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
E.
relativeToEasternTime
Indicates that the timing or occurrence of an event is specified or interpreted with respect to the Eastern Time zone.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:29 p.m.