Triple
T20752634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trimble, Ohio |
E510764
|
entity |
| Predicate | hasLocalTimeZoneAbbreviation |
P67797
|
FINISHED |
| Object | EST |
—
|
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: EST | Statement: [Trimble, Ohio, hasLocalTimeZoneAbbreviation, EST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalTimeZoneAbbreviation Context triple: [Trimble, Ohio, hasLocalTimeZoneAbbreviation, EST]
-
A.
includesTimeZoneAbbreviation
chosen
Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
-
B.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
C.
hasLocalizedTimeRules
Indicates that an entity applies specific time-related rules or conventions that are tailored to a particular locale or region.
-
D.
hasStandardTimeZone
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
E.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22be6588190b137193cb3184fc0 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.