Triple
T35077960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Native Client |
E1012355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sandboxing technology |
C55773
|
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: sandboxing technology Context triple: [Google Native Client, instanceOf, sandboxing technology]
-
A.
sandboxing tool
chosen
A sandboxing tool is a security mechanism that isolates applications or code in a controlled environment to prevent them from affecting the host system or accessing unauthorized resources.
-
B.
software security technology
Software security technology encompasses the tools, techniques, and practices designed to protect software systems from vulnerabilities, attacks, and unauthorized access throughout their lifecycle.
-
C.
hardware-based security technology
Hardware-based security technology refers to dedicated physical components and devices designed to protect systems and data by enforcing security functions at the hardware level, independent of or in conjunction with software controls.
-
D.
OS-level isolation mechanism
An OS-level isolation mechanism is a system feature that separates processes or workloads into distinct, controlled environments to prevent interference, enhance security, and manage resource usage.
-
E.
session border controller
A session border controller is a network device that manages, secures, and controls real-time communication sessions (such as VoIP and video) at the borders between different IP networks.
- F. None of above.
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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.