Triple
T34712347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socastee, South Carolina |
E1000679
|
entity |
| Predicate | locatedInTimeZoneOffsetDSTUTC |
—
|
GENERATED |
| Object | −04: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: locatedInTimeZoneOffsetDSTUTC Context triple: [Socastee, South Carolina, locatedInTimeZoneOffsetDSTUTC, −04:00]
-
A.
locatedInTimeZoneUTCOffsetDST
chosen
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
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.
timeZoneOffsetDestination
Indicates the time difference (offset from a reference time, typically UTC) that applies to the destination location in a temporal or travel-related context.
-
E.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.