Triple
T28507832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSWP |
E721403
|
entity |
| Predicate | belongsToCertificationPortfolioOf |
P18121
|
FINISHED |
| Object | Offensive Security |
—
|
NE NERFINISHED |
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: Offensive Security | Statement: [OSWP, belongsToCertificationPortfolioOf, Offensive Security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCertificationPortfolioOf Context triple: [OSWP, belongsToCertificationPortfolioOf, Offensive Security]
-
A.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
B.
belongsToPortfolio
chosen
Indicates that something is included as a component or asset within a particular portfolio.
-
C.
relatedCertification
Indicates that one certification is associated with, connected to, or relevant to another certification in some meaningful way.
-
D.
notableWorkCertification
Indicates that a certification is a notable or significant work associated with an entity.
-
E.
certificationProgramOf
Indicates that one entity is a certification program that is offered, managed, or owned by another entity.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 3:10 a.m.