Triple
T8290482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Configuration Manager |
E193879
|
entity |
| Predicate | securityCapability |
P55904
|
FINISHED |
| Object | endpoint protection policy management |
—
|
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: endpoint protection policy management | Statement: [Configuration Manager, securityCapability, endpoint protection policy management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCapability Context triple: [Configuration Manager, securityCapability, endpoint protection policy management]
-
A.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
-
B.
capabilityType
chosen
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
D.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
E.
operationalCapability
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9b65e0819083ddc82fb7c4a5f3 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.