Triple
T28507826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSWP |
E721403
|
entity |
| Predicate | preparationCourseProvider |
P29437
|
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, preparationCourseProvider, Offensive Security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparationCourseProvider Context triple: [OSWP, preparationCourseProvider, Offensive Security]
-
A.
offersCertificationPreparationFor
chosen
Indicates that an entity provides training or resources specifically designed to prepare individuals for obtaining a particular certification.
-
B.
courseCup
Indicates that a particular cup is used for or associated with serving a specific course in a meal.
-
C.
onCourse
Indicates that one entity is currently enrolled in, participating in, or following a particular course.
-
D.
currentCourseEstablishedBy
Indicates that the currently offered course was created, founded, or formally established by a specific entity (such as a person or organization).
-
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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:10 a.m.