Triple
T1718463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppArmor |
E37339
|
entity |
| Predicate | kernelInterface |
P11686
|
FINISHED |
| Object | /sys/kernel/security/apparmor |
—
|
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: /sys/kernel/security/apparmor | Statement: [AppArmor, kernelInterface, /sys/kernel/security/apparmor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kernelInterface Context triple: [AppArmor, kernelInterface, /sys/kernel/security/apparmor]
-
A.
kernelType
Indicates the specific kind or category of kernel associated with or used by an entity.
-
B.
primaryKernelType
Indicates that one entity is the main or default kernel type associated with another entity.
-
C.
usesInterface
chosen
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
D.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
E.
kitType
Indicates the specific category or configuration of a kit associated with an entity or activity.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.