Triple
T27663094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWASP Top 10 protections |
E697168
|
entity |
| Predicate | includesControlType |
P196357
|
FINISHED |
| Object | secure coding practices |
—
|
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: secure coding practices | Statement: [OWASP Top 10 protections, includesControlType, secure coding practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesControlType Context triple: [OWASP Top 10 protections, includesControlType, secure coding practices]
-
A.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
B.
typeOfControl
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
-
C.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
D.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
-
E.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: April 27, 2026, 2:37 p.m.