Triple
T15637403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTC−11 time zone |
E375981
|
entity |
| Predicate | isOneOfLastTimeZonesToExperienceDay |
P119556
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UTC−11 time zone, isOneOfLastTimeZonesToExperienceDay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfLastTimeZonesToExperienceDay Context triple: [UTC−11 time zone, isOneOfLastTimeZonesToExperienceDay, true]
-
A.
isOneOfLatestTimeZones
Indicates that an entity belongs to the most recently defined or updated set of time zones in the system.
-
B.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
C.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
D.
DSTAlternativePreviouslyUsedUTCOffset
Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
-
E.
observesDaylightSavingTimeInSomeRegions
Indicates that the entity follows daylight saving time practices, but only in certain parts or regions of its jurisdiction or coverage area.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.