Triple
T10922653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauritius Time |
E257984
|
entity |
| Predicate | observesLeapSeconds |
P12853
|
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: [Mauritius Time, observesLeapSeconds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesLeapSeconds Context triple: [Mauritius Time, observesLeapSeconds, yes]
-
A.
usesLeapSeconds
chosen
Indicates that a timekeeping system or standard incorporates leap seconds to adjust for irregularities in Earth's rotation.
-
B.
leapSecondAdjustment
Indicates a corrective time adjustment applied to synchronize a clock or time scale with leap seconds introduced into official timekeeping.
-
C.
leapSecondPurpose
Indicates the reason or intended function for which a leap second is introduced or used.
-
D.
observesDaylightSavingTime
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
E.
observesDSTOffset
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708d1fb88190bb33b72d4330ce11 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.