Triple
T35934079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rural Municipality of Riverside No. 168 |
E1039246
|
entity |
| Predicate | isInTimeZoneAbbreviation |
P67797
|
FINISHED |
| Object | CST |
—
|
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: CST | Statement: [Rural Municipality of Riverside No. 168, isInTimeZoneAbbreviation, CST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInTimeZoneAbbreviation Context triple: [Rural Municipality of Riverside No. 168, isInTimeZoneAbbreviation, CST]
-
A.
isInTimeZoneOffset
Indicates that one temporal entity occurs within, or is associated with, a specific time zone offset relative to a reference time standard (such as UTC).
-
B.
includesTimeZoneAbbreviation
chosen
Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
-
C.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
D.
isDaylightSavingShift
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
-
E.
isAbbreviation
Indicates that one term is a shortened or abbreviated form of another term.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.