Triple
T17598415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swagger |
E428632
|
entity |
| Predicate | ownedBy |
P347
|
FINISHED |
| Object | SmartBear Software |
E426649
|
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: SmartBear Software | Statement: [Swagger, ownedBy, SmartBear Software]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SmartBear Software Context triple: [Swagger, ownedBy, SmartBear Software]
-
A.
SmartBear Software
chosen
SmartBear Software is a software company known for its tools that support API development, testing, and monitoring, including stewardship of the popular Swagger ecosystem.
-
B.
PortSwigger Ltd
PortSwigger Ltd is a cybersecurity company best known for creating Burp Suite, a widely used web application security testing platform.
-
C.
Checkmarx
Checkmarx is a cybersecurity company specializing in application security testing solutions that help organizations identify and remediate vulnerabilities in their software code.
-
D.
Rapid7
Rapid7 is a cybersecurity company known for providing vulnerability management, incident detection, and penetration testing solutions.
-
E.
Burp Suite
Burp Suite is a popular integrated platform for web application security testing, widely used by penetration testers to identify and exploit vulnerabilities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a020a8d230c8190adadb2464e208324 |
completed | May 11, 2026, 4:57 p.m. |
Created at: April 10, 2026, 5:51 a.m.