Triple
T17838754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vacherie, Louisiana |
E445463
|
entity |
| Predicate | hasDaylightSavingTimeAbbreviation |
P2161
|
FINISHED |
| Object | CDT |
—
|
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: CDT | Statement: [Vacherie, Louisiana, hasDaylightSavingTimeAbbreviation, CDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDaylightSavingTimeAbbreviation Context triple: [Vacherie, Louisiana, hasDaylightSavingTimeAbbreviation, CDT]
-
A.
DSTAbbreviation
chosen
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
daylightSavingTimeName
Indicates the specific name or label used for the time zone during daylight saving time.
-
C.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
D.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
-
E.
observesDaylightSavingTime
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d29830c81909fa3ef5a352921b8 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.