Triple
T982987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Atomic Time |
E21211
|
entity |
| Predicate | leapSecondsApplied |
P12853
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [International Atomic Time, leapSecondsApplied, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leapSecondsApplied Context triple: [International Atomic Time, leapSecondsApplied, no]
-
A.
leapSecondAdjustment
Indicates a corrective time adjustment applied to synchronize a clock or time scale with leap seconds introduced into official timekeeping.
-
B.
usesLeapSeconds
chosen
Indicates that a timekeeping system or standard incorporates leap seconds to adjust for irregularities in Earth's rotation.
-
C.
leapSecondPurpose
Indicates the reason or intended function for which a leap second is introduced or used.
-
D.
offsetSeconds
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
E.
differenceFromTAI
Indicates the degree or nature of deviation between something and a reference point defined as TAI (e.g., a target, standard, or baseline associated with TAI).
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.