Triple

T29406485
Position Surface form Disambiguated ID Type / Status
Subject Red Hat Enterprise Linux Atomic Host E745787 entity
Predicate updateGranularity P167149 FINISHED
Object host-level atomic updates 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: host-level atomic updates | Statement: [Red Hat Enterprise Linux Atomic Host, updateGranularity, host-level atomic updates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: updateGranularity
Context triple: [Red Hat Enterprise Linux Atomic Host, updateGranularity, host-level atomic updates]
  • A. scalingGranularity
    Indicates the level of detail or resolution at which a quantity, process, or system is adjusted or scaled.
  • B. timeGranularity
    Indicates the level of temporal detail or precision at which an event, measurement, or relationship is defined (e.g., seconds, days, months).
  • C. backupGranularity
    Indicates the level of detail or scope (such as file, folder, or system level) at which backup operations are performed.
  • D. timeTravelGranularity
    Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
  • E. granularityLevel
    Indicates the degree of detail or resolution at which something is specified, measured, or analyzed within a given context.
  • 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_69f0a79eb7d081908c67197a5f347e68 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66a35247c8190acfba4d40db8c210 completed May 2, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69f66339175c819080bd70f0ff7057b1 completed May 2, 2026, 8:48 p.m.
PDg Predicate description generation batch_69f663ff176c8190aaadb475f75daee4 completed May 2, 2026, 8:52 p.m.
Created at: April 28, 2026, 2:54 p.m.