Triple
T27584740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computation Independent Model |
E699664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | model-driven architecture concept |
C47308
|
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: model-driven architecture concept Context triple: [Computation Independent Model, instanceOf, model-driven architecture concept]
-
A.
software architecture concept
A software architecture concept is an abstract, high-level idea or pattern that defines how software system components are organized, interact, and evolve to meet functional and non-functional requirements.
-
B.
software architecture pattern
A software architecture pattern is a reusable, high-level design blueprint that defines the structure, interactions, and responsibilities of components within a software system to address recurring architectural problems.
-
C.
software component model
A software component model is a conceptual framework that defines how modular, reusable software units are specified, composed, and interact within a system.
-
D.
software configuration model
A software configuration model is an abstract representation that defines and organizes the configurable parameters, components, and their relationships within a software system to control its behavior and deployment.
-
E.
modeling framework
chosen
A modeling framework is a structured set of concepts, methods, and tools used to construct, analyze, and interpret representations of real-world systems or phenomena.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.