Triple

T32536296
Position Surface form Disambiguated ID Type / Status
Subject OWASP E831598 entity
Predicate produces P490 FINISHED
Object OWASP Testing Guide
The OWASP Testing Guide is a comprehensive manual that outlines best practices, methodologies, and checklists for assessing and improving the security of web applications.
 E2009439 NE 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: OWASP Testing Guide | Statement: [OWASP, produces, OWASP Testing Guide]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: OWASP Testing Guide
Triple: [OWASP, produces, OWASP Testing Guide]
Generated description
The OWASP Testing Guide is a comprehensive manual that outlines best practices, methodologies, and checklists for assessing and improving the security of web applications.

Provenance (5 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c57062c481908b041788842c5990 completed May 3, 2026, 3:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347076694c8190a639957d285c3fff completed June 18, 2026, 10:25 p.m.
NEDg Description generation batch_6a3471350ec08190ae5394b2a8028840 completed June 18, 2026, 10:29 p.m.
NED2 Entity disambiguation (via description) batch_6a3471d84d708190bd56542c6f09ba30 completed June 18, 2026, 10:31 p.m.
Created at: May 1, 2026, 1:01 a.m.