Triple
T1527205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladivostok Time |
E32360
|
entity |
| Predicate | usedForCivilTimeInRegion |
P15575
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Vladivostok Time, usedForCivilTimeInRegion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForCivilTimeInRegion Context triple: [Vladivostok Time, usedForCivilTimeInRegion, yes]
-
A.
usedForCivilTimeIn
chosen
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
observesDaylightSavingTimeInSomeRegions
Indicates that the entity follows daylight saving time practices, but only in certain parts or regions of its jurisdiction or coverage area.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
- 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.