Triple
T22642811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Recife |
E558875
|
entity |
| Predicate | historicalDSTUse |
P29832
|
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: [America/Recife, historicalDSTUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDSTUse Context triple: [America/Recife, historicalDSTUse, yes]
-
A.
historicalDSTUsage
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.
hasHistoricalPermanentDSTExperiment
Indicates that an entity has undergone a historically significant, long-term or permanent daylight saving time experiment or trial.
-
C.
DSTAlternativePreviouslyUsedUTCOffset
Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
-
D.
previouslyObservedDST
chosen
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
-
E.
DSTNotRegularSince
Indicates that daylight saving time has not been regularly observed in the specified location since a given point in time.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703577948190ae044df4f8500bfe |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.