Triple

T33230583
Position Surface form Disambiguated ID Type / Status
Subject seL4: Formal Verification of an OS Kernel E850681 entity
Predicate propertyVerified P34351 FINISHED
Object functional correctness 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: functional correctness | Statement: [seL4: Formal Verification of an OS Kernel, propertyVerified, functional correctness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: propertyVerified
Context triple: [seL4: Formal Verification of an OS Kernel, propertyVerified, functional correctness]
  • A. propertyStatus chosen
    Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
  • B. dataTypeVerified
    Indicates that the data’s type has been checked and confirmed to match the expected or required type.
  • C. propertyHeld
    Indicates that a particular property is possessed, owned, or controlled by a specified entity.
  • D. ownedProperty
    Indicates that one entity possesses legal ownership or control over another entity as property.
  • E. securedStatus
    Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
  • 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_69f349613f988190a1eb75467d167122 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:30 a.m.