Triple
T2335931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Standard Time |
E44309
|
entity |
| Predicate | DSTcounterpartAbbreviation |
P27220
|
FINISHED |
| Object | PDT |
—
|
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: PDT | Statement: [Pacific Standard Time, DSTcounterpartAbbreviation, PDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTcounterpartAbbreviation Context triple: [Pacific Standard Time, DSTcounterpartAbbreviation, PDT]
-
A.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
DSTcounterpart
chosen
Indicates a correspondence between two time-related entities that are equivalent except for a daylight saving time adjustment.
-
C.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
D.
daylightSavingTimeName
Indicates the specific name or label used for the time zone during daylight saving time.
-
E.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.