Triple

T12701584
Position Surface form Disambiguated ID Type / Status
Subject Time Machine (Mac OS X feature) E303474 entity
Predicate backupGranularity P106423 FINISHED
Object block-level changes 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: block-level changes | Statement: [Time Machine (Mac OS X feature), backupGranularity, block-level changes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: backupGranularity
Context triple: [Time Machine (Mac OS X feature), backupGranularity, block-level changes]
  • A. timeTravelGranularity
    Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
  • B. controlGranularity
    Indicates the level of detail or fineness with which control or regulation is applied within a given process or system.
  • C. reservationGranularity
    Indicates the level of detail or unit (such as time, quantity, or capacity) at which a reservation can be specified or managed.
  • D. billingGranularity
    Indicates the level of detail or unit (such as per item, per hour, or per month) at which charges are calculated and presented in billing.
  • E. encryptionGranularity
    Indicates the level of detail or scope at which data is encrypted within a system or process.
  • 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_69d7bdef90d48190b46b88270e780946 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d962a32c6481908ddaddae4ea267bf completed April 10, 2026, 8:50 p.m.
PD Predicate disambiguation batch_69d960be63f081908a5ef5ef17a311bf completed April 10, 2026, 8:42 p.m.
PDg Predicate description generation batch_69d96297b81c819081ad1432dc5f15f4 completed April 10, 2026, 8:50 p.m.
Created at: April 9, 2026, 5:22 p.m.