Triple
T4253056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Standard Time |
E95902
|
entity |
| Predicate | DSTObservedHistorically |
P4819
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Standard Time, DSTObservedHistorically, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTObservedHistorically Context triple: [National Standard Time, DSTObservedHistorically, yes]
-
A.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
B.
historicalDSTUsage
chosen
Indicates that there was a period in the past when the entity or location observed daylight saving time, even if it may not do so currently.
-
C.
previouslyObservedDST
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
-
D.
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.
-
E.
hasHistoricalPermanentDSTExperiment
Indicates that an entity has undergone a historically significant, long-term or permanent daylight saving time experiment or trial.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebc98e08190915ac309a51ef87f |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.