Triple
T3938536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryans Road, Maryland |
E90973
|
entity |
| Predicate | timeZoneDaylightSaving |
P384
|
FINISHED |
| Object | UTC−04:00 |
—
|
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: UTC−04:00 | Statement: [Bryans Road, Maryland, timeZoneDaylightSaving, UTC−04:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneDaylightSaving Context triple: [Bryans Road, Maryland, timeZoneDaylightSaving, UTC−04:00]
-
A.
daylightSavingTimeHemisphere
Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
observesDaylightSavingTime
chosen
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
D.
timeZoneOriginDST
Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
-
E.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.