Triple

T8220811
Position Surface form Disambiguated ID Type / Status
Subject ReFS E192052 entity
Predicate metadataResilience P14772 FINISHED
Object uses checksums for metadata 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: uses checksums for metadata | Statement: [ReFS, metadataResilience, uses checksums for metadata]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: metadataResilience
Context triple: [ReFS, metadataResilience, uses checksums for metadata]
  • A. recoveryCapability
    Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
  • B. metadataType
    Indicates that one entity specifies the kind or category of metadata associated with another entity.
  • C. reliabilityRecord
    Indicates that there exists a record or documentation capturing the reliability characteristics, performance, or history associated with an entity or relationship.
  • D. metadataLocation
    Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
  • E. preservationFactor chosen
    Indicates the degree to which something is protected, maintained, or kept intact over time, often moderating how much change, loss, or degradation occurs.
  • 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_69ca82c9a8ac81908b011c38698456e4 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb77c782a8819086019ab6bac05749 completed March 31, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69cb36af41e081909dee92b9bc4947f1 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:45 p.m.