Triple
T388563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coordinated Universal Time |
E8830
|
entity |
| Predicate | leapSecondAdjustment |
P12854
|
FINISHED |
| Object | 1 second |
—
|
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: 1 second | Statement: [Coordinated Universal Time, leapSecondAdjustment, 1 second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leapSecondAdjustment Context triple: [Coordinated Universal Time, leapSecondAdjustment, 1 second]
-
A.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
B.
offsetSeconds
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
C.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
-
D.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
E.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
- F. None of above. chosen
Provenance (4 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5988708190aa86d9460cecf050 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ebac09408190be802b96bb203d5f |
completed | Feb. 28, 2026, 1:20 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.