Triple
T3938820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Regina |
E90981
|
entity |
| Predicate | hasFixedUtcOffset |
P4886
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [America/Regina, hasFixedUtcOffset, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedUtcOffset Context triple: [America/Regina, hasFixedUtcOffset, true]
-
A.
isFixedOffsetFromUTC
chosen
Indicates that one time-related entity consistently differs from Coordinated Universal Time (UTC) by a specific, unchanging offset.
-
B.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
C.
sameUTCOffsetAs
Indicates that two time-related entities share the same offset from Coordinated Universal Time (UTC), regardless of their specific time zones or locations.
-
D.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
E.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
- 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_69aeedfb12b88190a6ca6574b1aadb6e |
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.