Triple
T11655177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | runc |
E276996
|
entity |
| Predicate | supportsSeccomp |
P33737
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [runc, supportsSeccomp, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSeccomp Context triple: [runc, supportsSeccomp, true]
-
A.
hasSecuritySupport
Indicates that one entity provides security-related assistance, maintenance, or protection services for another entity.
-
B.
supportsIntelSGX
Indicates that one entity provides compatibility with or functional support for Intel Software Guard Extensions (Intel SGX) used by another entity.
-
C.
supportsMemoryProtection
Indicates that one entity provides mechanisms to prevent unauthorized access or interference with another entity’s memory space.
-
D.
hasSecurityExtension
chosen
Indicates that an entity is associated with, or equipped with, an additional component or feature that enhances its security.
-
E.
supportsAES-NI
Indicates that an entity (typically hardware or software) provides support for the AES-NI (Advanced Encryption Standard New Instructions) set of CPU instructions used to accelerate AES encryption and decryption operations.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.