Triple
T27888242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Atlas APIs |
E705285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software interface collection |
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: software interface collection Context triple: [Apache Atlas APIs, instanceOf, software interface collection]
-
A.
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.
-
B.
software environment collection
A software environment collection is an organized set of predefined, configurable runtime environments (including tools, libraries, and dependencies) that can be selected, combined, and managed to support diverse software development, testing, and deployment needs.
-
C.
system interface
A system interface is the defined boundary and set of interaction mechanisms through which different system components or external users communicate with and control a software or hardware system.
-
D.
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.
-
E.
statistical software interface
A statistical software interface is the user-facing layer that enables users to input data, specify analyses, run statistical procedures, and visualize results through graphical controls, command syntax, or APIs.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:34 p.m.