Triple
T4927008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Laurent Borough |
E110600
|
entity |
| Predicate | isLocatedInDSTTimeZone |
P44122
|
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: [Saint-Laurent Borough, isLocatedInDSTTimeZone, UTC−04:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInDSTTimeZone Context triple: [Saint-Laurent Borough, isLocatedInDSTTimeZone, UTC−04:00]
-
A.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
-
B.
isDaylightSavingShift
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
-
C.
hasDSTComponent
Indicates that something includes or is associated with a component related to Daylight Saving Time (DST) behavior or configuration.
-
D.
DSTIsAheadOfUTC
Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
-
E.
observesDSTOffset
chosen
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70354bd081909291a43439f42ed3 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.