Triple
T18721276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Denver |
E457778
|
entity |
| Predicate | dstEndRuleTypical |
P16241
|
FINISHED |
| Object | first Sunday in November |
—
|
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: first Sunday in November | Statement: [America/Denver, dstEndRuleTypical, first Sunday in November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstEndRuleTypical Context triple: [America/Denver, dstEndRuleTypical, first Sunday in November]
-
A.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
B.
typicalEndDay
Indicates the usual or most common day on which an event, activity, or state typically concludes.
-
C.
dstRulePattern
Indicates a rule-based pattern that specifies or constrains the characteristics of a destination in a relationship or process.
-
D.
dstTransitionRuleType
chosen
Indicates the type or category of rule that governs how a system transitions into or out of daylight saving time.
-
E.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56abadca08190ab1e699b7dcc0c4d |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.