Triple
T5419653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis Río Colorado, Sonora |
E121215
|
entity |
| Predicate | timezoneStandardName |
P11952
|
FINISHED |
| Object | Mountain Standard Time |
—
|
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: Mountain Standard Time | Statement: [San Luis Río Colorado, Sonora, timezoneStandardName, Mountain Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneStandardName Context triple: [San Luis Río Colorado, Sonora, timezoneStandardName, Mountain Standard Time]
-
A.
timeZoneName
chosen
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
B.
UTCOffsetStandardTime
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
C.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
D.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
-
E.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e8f1cc81908b997f8a417697c0 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.