Triple
T27612364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | supportsLeapSecondInfo |
P199809
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Time Protocol, supportsLeapSecondInfo, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLeapSecondInfo Context triple: [Time Protocol, supportsLeapSecondInfo, false]
-
A.
usesLeapSeconds
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.
hasLeapYearFrequency
Indicates how often leap years occur within a given temporal pattern or calendar system.
-
E.
doesNotUseLeapMonths
Indicates that the referenced calendar or timekeeping system does not incorporate leap months to adjust for discrepancies between its cycle and the astronomical year.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: April 27, 2026, 2:11 p.m.