Triple
T12092563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Indiana/Indianapolis |
E287982
|
entity |
| Predicate | historicallyObservedDST |
P4819
|
FINISHED |
| Object | irregular |
—
|
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: irregular | Statement: [America/Indiana/Indianapolis, historicallyObservedDST, irregular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyObservedDST Context triple: [America/Indiana/Indianapolis, historicallyObservedDST, irregular]
-
A.
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.
-
B.
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.
-
C.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
D.
DSTObservedInCountry
Indicates that daylight saving time (DST) is implemented or observed within a given country.
-
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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.