Triple
T23078363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morzhovoi |
E575396
|
entity |
| Predicate | locatedInUtsOffset |
P10251
|
FINISHED |
| Object | UTC−09: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: UTC−09:00 | Statement: [Morzhovoi, locatedInUtsOffset, UTC−09:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUtsOffset Context triple: [Morzhovoi, locatedInUtsOffset, UTC−09:00]
-
A.
locatedInTimeZoneUTCOffsetDST
Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
-
B.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
-
C.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
D.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
E.
usesUTCOffset
chosen
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c6572d88190afab0dfa960a85dd |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:56 p.m.