Triple
T1527199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladivostok Time |
E32360
|
entity |
| Predicate | DSTCurrentlyObserved |
P8084
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Vladivostok Time, DSTCurrentlyObserved, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTCurrentlyObserved Context triple: [Vladivostok Time, DSTCurrentlyObserved, false]
-
A.
DSTobserved
chosen
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
B.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
C.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
D.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
E.
DSThemisphere
Indicates a relationship where one entity is located in, or belongs to, a particular hemisphere relative to another reference frame or system.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.