Triple
T28821304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burp Extender |
E727771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software extension framework |
C55263
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: software extension framework Context triple: [Burp Extender, instanceOf, software extension framework]
-
A.
browser extension framework
A browser extension framework is a structured set of APIs, tools, and conventions that simplifies building, integrating, and managing extensions across one or more web browsers.
-
B.
programming language extension
A programming language extension is an add-on or modification that enhances an existing language with new syntax, features, or capabilities without fundamentally changing its core semantics.
-
C.
software framework category
A software framework category is a conceptual grouping that classifies software frameworks based on shared characteristics such as purpose, architecture, technology stack, or domain of application.
-
D.
open-source framework
An open-source framework is a publicly accessible, collaboratively developed software foundation that provides reusable components and tools to simplify and accelerate application development.
-
E.
integrated development environment framework
An integrated development environment framework is a modular, extensible platform that provides core services and tools—such as editors, debuggers, build systems, and plug-in architectures—for constructing and customizing full-featured software development environments.
- F. None of above. chosen
Provenance (1 batch)
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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:34 a.m.