Triple
T76552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American time zones |
E1528
|
entity |
| Predicate | hasVariation |
P455
|
FINISHED |
| Object | regions that do not observe daylight saving time |
—
|
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: regions that do not observe daylight saving time | Statement: [North American time zones, hasVariation, regions that do not observe daylight saving time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariation Context triple: [North American time zones, hasVariation, regions that do not observe daylight saving time]
-
A.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
C.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
E.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2559892dc81909303f2eefdc0025f |
completed | Feb. 28, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69a24eaf99e481908e8d314577e22ecf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.