Triple
T1718443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppArmor |
E37339
|
entity |
| Predicate | profileDirectory |
P31920
|
FINISHED |
| Object | /etc/apparmor.d |
—
|
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: /etc/apparmor.d | Statement: [AppArmor, profileDirectory, /etc/apparmor.d]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: profileDirectory Context triple: [AppArmor, profileDirectory, /etc/apparmor.d]
-
A.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
B.
mediaProfile
Indicates a relationship where a media-related profile or account is associated with an entity, typically representing its presence or identity in media contexts.
-
C.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
D.
academicProfile
Indicates the relationship that captures an entity’s academic background, qualifications, and scholarly activities or achievements.
-
E.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
- 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_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. |
| PDg | Predicate description generation | batch_69ab5c7780bc81909fc6e173a216cb0b |
completed | March 6, 2026, 11 p.m. |
Created at: March 4, 2026, 7:30 p.m.