Triple
T11126781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Integrity Protection |
E263158
|
entity |
| Predicate | protectsDirectory |
P1040
|
FINISHED |
| Object | /System |
—
|
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: /System | Statement: [System Integrity Protection, protectsDirectory, /System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsDirectory Context triple: [System Integrity Protection, protectsDirectory, /System]
-
A.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
-
B.
protects
chosen
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
E.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82fc5f88190b34c55de3d50f6a7 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.