Triple
T13299836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardwick, Minnesota |
E316778
|
entity |
| Predicate | isInTimeZoneRegion |
P109
|
FINISHED |
| Object | Central United States time region |
—
|
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: Central United States time region | Statement: [Hardwick, Minnesota, isInTimeZoneRegion, Central United States time region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInTimeZoneRegion Context triple: [Hardwick, Minnesota, isInTimeZoneRegion, Central United States time region]
-
A.
locatedInTimeZone
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
C.
isNeighboringTimeZoneTo
Indicates that two time zones are directly adjacent to each other, typically sharing a common boundary or differing by one standard time offset step.
-
D.
isNorthAmericanTimeZone
Indicates that a given time zone is located within the North American region.
-
E.
isIslandTimeZone
Indicates that a given time zone is associated with or specific to an island or group of islands.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.