Triple
T11016530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPENSTEP |
E260378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | application programming interface specification |
C6413
|
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: application programming interface specification Context triple: [OPENSTEP, instanceOf, application programming interface specification]
-
A.
system interface specification
chosen
A system interface specification is a detailed description of how different system components or external systems interact, defining the data formats, protocols, operations, and constraints that govern their communication.
-
B.
web service specification
A web service specification is a formal, technology-agnostic description of a web service’s interfaces, operations, data formats, and communication protocols that enables consistent implementation and integration across different systems.
-
C.
interface
An interface is an abstract contract that defines a set of methods or behaviors a class must implement without specifying how those behaviors are carried out.
-
D.
interoperability specification suite
An interoperability specification suite is a coordinated set of technical standards, protocols, and guidelines designed to ensure that diverse systems, components, or organizations can reliably exchange and correctly interpret data and functionality.
-
E.
open source software interface
An open source software interface is a publicly accessible set of interaction points, such as APIs or user interfaces, whose underlying code is openly available for use, modification, and distribution under an open source license.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.