Triple
T28615031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Access Protection |
E724254
|
entity |
| Predicate | supportsRemediation |
P203304
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Network Access Protection, supportsRemediation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRemediation Context triple: [Network Access Protection, supportsRemediation, true]
-
A.
hasRemediationStatus
Indicates the current state or progress of remediation efforts applied to an identified issue, risk, or non-compliance.
-
B.
hasRemediationGoal
Indicates that an entity is associated with a specific goal or objective aimed at correcting, mitigating, or improving a problem or deficiency.
-
C.
remediationActivity
Indicates an action or process undertaken to correct, mitigate, or resolve an identified issue, risk, or non-compliance.
-
D.
requiresMitigation
Indicates that something poses a risk or issue that must be addressed through specific mitigation actions or measures.
-
E.
supportsInstruction
Indicates that one entity provides assistance, resources, or functionality that enables or facilitates the instruction or teaching activities of another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_6a01531a3a4c8190ac8cb040cc36e96b |
completed | May 11, 2026, 3:55 a.m. |
Created at: April 28, 2026, 4:31 a.m.