Triple
T35679392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ortacesus |
E1030961
|
entity |
| Predicate | locatedInTimeZoneOffsetFromUTC |
—
|
GENERATED |
| Object | +01:00 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeZoneOffsetFromUTC Context triple: [Ortacesus, locatedInTimeZoneOffsetFromUTC, +01: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.
locatedInTimeZone
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
C.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
D.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
-
E.
partlyLocatedInTimeZone
Indicates that an entity’s extent overlaps multiple time zones, with at least part of it falling within the specified time zone.
- F. None of above.
Provenance (1 batch)
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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.