Triple
T30692394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitareti |
E781363
|
entity |
| Predicate | timeZoneCountryStandard |
P169211
|
FINISHED |
| Object | Georgia 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: Georgia Standard Time | Statement: [Pitareti, timeZoneCountryStandard, Georgia Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneCountryStandard Context triple: [Pitareti, timeZoneCountryStandard, Georgia Standard Time]
-
A.
countryTimeStandardFor
chosen
Indicates that a specific time standard (such as a time zone or time-keeping system) is officially used by a given country.
-
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.
timeZoneRegionType
Indicates the classification of a time zone based on the type of geographic or administrative region it is associated with.
-
D.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
E.
timeZoneEndpoint
Indicates a connection or boundary point where a specific time zone applies or is defined.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:33 p.m.