Triple
T1718383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SELinux |
E37338
|
entity |
| Predicate | policyLanguage |
P31919
|
FINISHED |
| Object | SELinux policy language |
—
|
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: SELinux policy language | Statement: [SELinux, policyLanguage, SELinux policy language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyLanguage Context triple: [SELinux, policyLanguage, SELinux policy language]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
policyFramework
Indicates the overarching set of principles, rules, and guidelines that govern how decisions and actions are structured and carried out within a particular domain or context.
-
C.
lawStatement
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
D.
policyContext
Indicates the situational or regulatory framework within which a policy is defined, interpreted, or applied.
-
E.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
- 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.